Does Strikingly support custom meta titles and descriptions?

Yes. Each Strikingly page has SEO settings (Site Settings → SEO) for a custom page title and meta description. Simple sites that use multiple sections on a single page have one global SEO title and description — Strikingly\'s single-page architecture means there is no per-section meta tag control. Multi-page Strikingly sites (on paid plans) have per-page SEO settings. The title tag field accepts up to 60 characters and the description up to 155 characters.

Can I add JSON-LD structured data to a Strikingly website?

Yes, on paid Strikingly plans (Pro and above) that support the HTML embed widget or custom HTML injection. Add a Custom HTML widget to the page, paste your JSON-LD script block, and set the widget to "hidden" so it doesn\'t display visually. Alternatively, paid Strikingly plans allow custom code injection in site settings (Analytics section) via a Google Analytics-style header code field — this is also usable for site-wide JSON-LD (Organisation, WebSite) but not for page-specific schema. Free Strikingly plans have no custom code injection capability.

Does Strikingly generate an automatic sitemap?

Yes. Strikingly automatically generates a sitemap.xml for all published sites, accessible at yourdomain.com/sitemap.xml. The sitemap is updated when new pages are published. Custom domains on paid plans are included in the sitemap with the custom domain URL. Strikingly submits the sitemap to Google Search Console automatically for sites connected via the built-in GSC integration, but manual submission through GSC is also available.

How does DeepSEOAnalysis help with Strikingly SEO?

DeepSEOAnalysis checks your Strikingly page\'s technical SEO health including: meta title and description quality, canonical tag correctness, structured data validity and completeness (checking whether your embedded JSON-LD has all required properties), real CrUX field data for Core Web Vitals (LCP, CLS, INP from real Chrome users visiting your Strikingly site), robots.txt analysis, and AI visibility scoring. Because Strikingly serves pages through its CDN infrastructure, CrUX field data is the most accurate indicator of how Google rates your page\'s performance — not Lighthouse lab scores.

Strikingly SEO audit

Strikingly is a single-page website builder popular for landing pages, portfolios, and simple business sites. It provides built-in meta tag settings, automatic sitemap generation, and HTTPS on custom domains — but custom JSON-LD structured data requires paid plans and HTML widget injection, and llms.txt is not achievable through Strikingly's standard interface. DeepSEOAnalysis audits your Strikingly site's actual technical health with real Chrome user performance data, not Lighthouse estimates.

Audit your Strikingly site free →

What we check on Strikingly sites

Meta tags and page SEO settings

Page title tag quality and keyword placement in Strikingly SEO settings
Meta description completeness and character count
Open Graph and Twitter Card tags (Strikingly auto-generates OG tags from SEO settings)
Single-page vs multi-page architecture and its impact on per-page meta control

Canonical tag and URL structure

Canonical tag correctness — Strikingly generates canonical tags pointing to custom domain or strikingly.com subdomain
Custom domain canonical vs Strikingly subdomain duplicate content risk
URL structure for multi-page Strikingly sites and slug quality
HTTPS enforcement on custom domains

JSON-LD structured data via HTML widget

Presence and validity of structured data injected via Custom HTML widget
Organisation and WebSite schema via header code injection (Pro plan)
FAQPage schema server-rendering — JSON-LD must be in initial HTML, not added via JavaScript
Property-level validation: which required fields are missing from each schema type

Sitemap and crawlability

Auto-generated sitemap.xml accessibility and URL coverage
robots.txt configuration — Strikingly's default allows all crawlers including AI bots
AI crawler access: GPTBot, ClaudeBot, PerplexityBot, Google-Extended allowed or blocked
llms.txt — not achievable via standard Strikingly; platform limitation

Core Web Vitals (real user data)

LCP: Strikingly's hero sections often use CSS background images rather than <img> elements — background images are not LCP-eligible for optimisation
CLS: Strikingly's column-based layouts and font loading cause layout shift on initial load
INP: Heavy Strikingly framework JavaScript including scroll animations creates interaction delay
CrUX field data — p75 real Chrome user performance vs Lighthouse lab scores

AI visibility and llms.txt

AI crawler access in robots.txt (Strikingly default: allow-all — beneficial for AI visibility)
llms.txt not deployable via standard Strikingly interface (platform limitation)
FAQPage schema achievable via HTML widget on paid plans — check server-rendering status
Question-heading ratio in page content: H2/H3 headings that are explicit questions
Content section length for AI extractability: average section under 400 words per heading

Strikingly SEO: platform constraints and workarounds

Strikingly's SEO ceiling is higher than many simple website builders because Pro plans allow Custom HTML widgets that can contain JSON-LD script blocks. For a single-page site, a hidden Custom HTML widget near the bottom of the page is the standard method for adding structured data — Organisation, WebSite, FAQPage, and LocalBusiness schema are all achievable this way. The JSON-LD must be in the initial server-rendered HTML to be read by Google; Strikingly's Custom HTML widget renders server-side, so this condition is met.

The primary Strikingly SEO limitation is the single-page architecture on free plans: one page means one meta title, one meta description, and one canonical URL, regardless of how many content sections the page has. Multi-page Strikingly sites (Simple, Pro, VIP plans) resolve this with per-page SEO settings. For sites that outgrow Strikingly's SEO capabilities, migrating to Webflow or a headless CMS provides full technical SEO control without sacrificing visual design ease.

AI visibility on Strikingly sites is constrained primarily by the inability to add an llms.txt file at the domain root via Strikingly's standard interface. The robots.txt (controlled by Strikingly) allows all crawlers by default, which benefits AI crawler access. FAQPage schema via Custom HTML widget provides the structured FAQ signal AI systems look for. The question-heading ratio (H2/H3 headings phrased as questions) is achievable in Strikingly's section heading fields. Content chunkability — keeping individual sections under 400 words per heading — is achievable with Strikingly's section-based editor.

Frequently asked questions

Does Strikingly support custom meta titles and descriptions?: Yes. Each Strikingly page has SEO settings (Site Settings → SEO) for a custom page title and meta description. Simple sites that use multiple sections on a single page have one global SEO title and description — Strikingly\'s single-page architecture means there is no per-section meta tag control. Multi-page Strikingly sites (on paid plans) have per-page SEO settings. The title tag field accepts up to 60 characters and the description up to 155 characters.
Can I add JSON-LD structured data to a Strikingly website?: Yes, on paid Strikingly plans (Pro and above) that support the HTML embed widget or custom HTML injection. Add a Custom HTML widget to the page, paste your JSON-LD script block, and set the widget to "hidden" so it doesn\'t display visually. Alternatively, paid Strikingly plans allow custom code injection in site settings (Analytics section) via a Google Analytics-style header code field — this is also usable for site-wide JSON-LD (Organisation, WebSite) but not for page-specific schema. Free Strikingly plans have no custom code injection capability.
Does Strikingly generate an automatic sitemap?: Yes. Strikingly automatically generates a sitemap.xml for all published sites, accessible at yourdomain.com/sitemap.xml. The sitemap is updated when new pages are published. Custom domains on paid plans are included in the sitemap with the custom domain URL. Strikingly submits the sitemap to Google Search Console automatically for sites connected via the built-in GSC integration, but manual submission through GSC is also available.
How does DeepSEOAnalysis help with Strikingly SEO?: DeepSEOAnalysis checks your Strikingly page\'s technical SEO health including: meta title and description quality, canonical tag correctness, structured data validity and completeness (checking whether your embedded JSON-LD has all required properties), real CrUX field data for Core Web Vitals (LCP, CLS, INP from real Chrome users visiting your Strikingly site), robots.txt analysis, and AI visibility scoring. Because Strikingly serves pages through its CDN infrastructure, CrUX field data is the most accurate indicator of how Google rates your page\'s performance — not Lighthouse lab scores.