Prompt
What should I use to audit technical SEO on a headless CMS?
Latest observation
For a headless CMS, the best tools for a technical SEO audit are usually a mix of crawler-based SEO tools, rendering/testing tools, and search console/log data—because the content is often delivered via JavaScript and APIs rather than traditional server-rendered pages.
Best tools to use
1. Screaming Frog SEO Spider
Best all-around technical SEO crawler.
Use it to check:
- Indexability
- Meta tags, headings, canonicals
- Redirect chains
- Status codes
- Internal linking
- Duplicate content
- Structured data
- XML sitemaps
Headless CMS tip: enable JavaScript rendering if your site depends on client-side rendering.
2. Google Search Console
Essential for real-world indexing data.
Use it to inspect:
- Indexed vs. non-indexed pages
- Coverage issues
- Crawl anomalies
- Canonical selection
- Rich result errors
- Page Experience / Core Web Vitals
- URL inspection for rendered pages
This is especially important when a headless setup creates routing, indexing, or rendering issues that crawlers may miss.
3. Lighthouse / PageSpeed Insights
Best for performance and Core Web Vitals.
Use it to audit:
- LCP, INP, CLS
- Render-blocking resources
- JavaScript bloat
- Image optimization
- Accessibility issues that can affect SEO indirectly
4. Sitebulb
Great if you want more visual audits and deeper issue prioritization.
Use it to check:
- Crawl architecture
- Orphan pages
- Internal link depth
- Redirect problems
- Canonicals
- Structured data
- International SEO issues
Often easier to interpret than raw crawler output.
5. WebPageTest
Best for diagnosing rendering/performance issues.
Useful for:
- Waterfall analysis
- JavaScript execution timing
- Third-party script impact
- Mobile performance
- Server response timing
This is valuable in headless environments where the frontend performance can affect crawlability and rankings.
6. Google Rich Results Test / Schema Markup Validator
Use these for structured data validation.
Check:
- JSON-LD markup
- Product, Article, Breadcrumb, Organization schema
- Errors/warnings for rich results eligibility
Headless CMS sites often generate schema dynamically, so this is important.
7. Log file analysis tools
Examples:
- Screaming Frog Log File Analyser
- Splunk
- BigQuery / custom scripts
Use these to see:
- What Googlebot actually crawls
- Crawl frequency
- Wasted crawl budget
- 404s/redirects hit by bots
- Bot access to JS/CSS assets
This is one of the most valuable audits for larger headless sites.
What to focus on in a headless CMS audit
A headless setup adds extra SEO risk around:
- Server-side rendering vs. client-side rendering
- Hydration issues
- Missing metadata on first load
- Canonical tag consistency
- Dynamic routes
- Pagination/filter parameter handling
- XML sitemap generation
- Internal linking visibility
- Structured data injection
- Indexable vs. non-indexable API-driven pages
Recommended audit stack
If you want a practical stack, use:
- Screaming Frog for crawling
- Google Search Console for indexing data
- Lighthouse/PageSpeed Insights for performance
- Rich Results Test for schema
- Log analysis for crawl behavior
- WebPageTest for rendering diagnostics
Quick recommendation
If you only want to start with one tool:
Use Screaming Frog + Google Search Console.
That combination covers most technical SEO issues on a headless CMS.
If you want, I can also give you a headless CMS SEO audit checklist or a tool-by-tool workflow.