Technical SEO Audit
Your content is fine. Something underneath it isn't.
Marketing or technical leads at established sites — including e-commerce catalogs — whose organic performance doesn’t match what they’re publishing.
Signs the problem is underneath the content
- Traffic dropped after a migration, replatform, or major redesign, and nobody can point to the exact cause.
- Search Console shows a growing number of pages "Crawled – currently not indexed."
- Core Web Vitals or INP is flagged in Search Console, and it's not obvious which template is responsible.
- Your product catalog generates thousands of filter and parameter URLs competing with each other for the same rankings.
- New pages take weeks to get indexed, and the assumption internally is "that’s just how Google works."
The six audits inside this report
- Indexation audit
- Which pages are indexed, excluded, and why
- Detected via: Search Console index coverage + full crawl
- Crawlability audit
- Robots.txt, internal-link depth, orphaned pages, redirect chains
- Detected via: Full-site crawl
- Core Web Vitals / INP report
- Real-user field data per template, not a lab simulation
- Detected via: CrUX field data + PageSpeed Insights
- JavaScript-rendering audit
- What Googlebot actually renders vs. what’s in the raw HTML
- Detected via: Rendered-vs-raw HTML diff
- Faceted-navigation & parameter audit
- Duplicate and thin pages generated by filters and sort parameters (the e-commerce angle)
- Detected via: Crawl + parameter pattern analysis
- Prioritized fix list
- Every finding ranked by estimated traffic impact, ready to hand to a developer
- Detected via: Manual review against baseline traffic
Not included
Implementation of fixes (delivered as an engineering-ready list, not built by default) · Content writing · Log-file analysis (Core tier — see Deep Crawl & Log-File Audit) · Paid media · Ongoing monitoring after the report · Guaranteed ranking outcomes
How we run this audit
Full crawl plus Search Console index coverage, pulled before anything else.
Each indexation or Vitals problem traced to a specific template, redirect or script — not filed under generic "technical debt."
Findings ranked by estimated traffic impact and handed over as an engineering-ready fix list.
A re-crawl against the baseline once fixes ship, to confirm the indexation or Vitals number actually moved.
A written audit in the same fixed excerpt format every client receives — findings, priority, and the reasoning behind each.
Evidence
The indexation findings, structured
What's indexed, what's excluded, and the specific reason for each exclusion, ranked by estimated traffic impact — that's the structure of every Core Technical Audit's indexation section. The panel alongside is an illustrative rendering, not a page from a live client report.
See the full artifact →
Two ways to run this audit.
foundation · STL-COR-TA
Core Technical Audit
Full crawlability, indexation and Core Web Vitals audit for sites up to ~5,000 URLs.
- A dedicated crawl run against your live site by hand, not an automated report with no review
- Direct access to the analyst who ran the audit, for questions after delivery
- One round of clarifying questions before the report is finalized
- The full deliverable set below, reported in the same fixed format every audit client receives
foundation · STL-DCL-TA
Deep Crawl & Log-File Audit
Everything in Core, plus real log-file analysis of what Googlebot actually crawls.
- Everything in the Core Technical Audit
- Manual review of your server log export against the crawl data
- A dedicated call to walk through the findings before the written report ships
- Direct access to the analyst for questions after delivery