A technical SEO audit is a structured review of how well search engines can crawl, render, index and understand your website, followed by a prioritized list of fixes. It checks the infrastructure under your content (status codes, robots.txt, sitemaps, canonical tags, internal links, JavaScript rendering, page speed and structured data) rather than the words on the page, and a good one ends with a plan your developers can actually ship.
This guide is for e-commerce and Shopify teams deciding whether they need an audit, what to expect from one and who should run it. You'll get what an audit covers, what the 2025 Web Almanac says about the most common technical gaps, the deliverables you should insist on, the step-by-step process, what drives cost (with the only published pricing survey we could verify) and a checklist for choosing who does the work. If you want the line-by-line checks themselves, use our technical SEO audit checklist.
What is a technical SEO audit?
Google describes search in three stages: it crawls pages, indexes what it finds and then serves results. A technical SEO audit tests each stage on your site. Can Googlebot reach the URLs that matter? Does it index the right version of each page, and only once? Can it see the content after JavaScript runs? Do real visitors get a fast, stable page? If any of those answers is no, even excellent content struggles to rank or to be cited in AI answers.
The audit is diagnostic, not a fix in itself. Its value is in the prioritization: which problems are costing you traffic and revenue, which are cosmetic and what order to fix them in.
Technical audit vs. other SEO audits
| Audit type | Main question | Typical inputs | Typical output |
|---|---|---|---|
| Technical SEO audit | Can search engines crawl, render and index the site correctly? | Site crawl, Search Console, server logs, Core Web Vitals field data | Prioritized fix list and developer tickets |
| Content audit | Which pages should be improved, merged or removed? | Traffic, rankings, conversions per URL | Keep, update, merge or prune decisions |
| On-page audit | Do titles, headings and copy match search intent? | Keyword data, page templates, SERP review | Template and copy changes |
| Backlink audit | Is the link profile helping or creating risk? | Link index data, anchor text | Outreach targets and cleanup notes |
| Full SEO audit | All of the above, ranked against each other | Everything above plus competitor benchmarks | One roadmap across teams |
For online stores, the technical audit usually comes first, because faceted navigation, product variants and app scripts create problems that no amount of content work can overcome. Our Shopify SEO audit guide covers the platform-specific version.
What a technical SEO audit covers
Scope varies by site, but a complete technical audit checks these eight areas. Each one maps to documented Google behavior, so findings can be tied back to official guidance instead of a tool's opinion.
1. Crawlability
Robots.txt rules, HTTP status codes, redirect chains, server errors and crawl paths. Google's documentation notes that a URL blocked in robots.txt is not fetched at all, and Google won't render JavaScript from blocked files. On Shopify, robots.txt is generated by default and can be customized with a robots.txt.liquid template; Shopify's developer docs advise saving a copy of the current output before you publish changes. Test rules with our robots.txt tester and chains with the redirect checker.
2. Indexation
Which URLs are indexed, which are excluded and why. The Page indexing report in Search Console is the primary source here, backed by URL Inspection for individual pages. Common store issues include filtered and sorted collection URLs, internal search pages and thin tag pages, which we cover in our guide to index bloat.
3. Canonicals and duplicate content
Google's canonicalization guide ranks the signals you control: redirects and rel="canonical" annotations are strong signals, and sitemap inclusion is a weak one, and the methods stack when combined. The audit checks that canonicals, internal links and sitemaps all point to the same preferred URL. Shopify's Dawn theme outputs a canonical tag from the canonical_url object, so most issues on Shopify come from apps, custom templates or internal links to non-canonical variants. See canonical tags for SEO.
4. Site architecture and internal links
Click depth, orphan pages, broken internal links and anchor text. Important collections and products should be reachable in a few clicks from the homepage. Our internal link checker and anchor text analyzer help with spot checks.
5. Rendering and JavaScript
Google processes JavaScript pages in three phases (crawling, rendering and indexing), and rendering is queued separately from crawling. The audit compares raw HTML with the rendered page to confirm that product content, prices, links and structured data exist after rendering.
6. Page experience and Core Web Vitals
Google's thresholds for a good experience, measured at the 75th percentile of page loads, are Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less and Cumulative Layout Shift of 0.1 or less. INP replaced FID as a Core Web Vital in March 2024. The audit should use field data from real users, not only lab scores.
7. Structured data
Product, Offer, Review, Breadcrumb and Organization markup, validated for errors and checked against what is visible on the page. Try our schema validator.
8. AI crawler access and machine readability
A modern audit also confirms that the crawlers behind AI search can reach your pages. That means checking robots.txt rules for the user agents the AI platforms document and making sure key content is in the HTML. See how to check if ChatGPT can crawl your website.
The most common technical gaps, by the numbers
The best public picture of the web's technical health is the HTTP Archive Web Almanac, which analyzes millions of pages from its crawl along with Chrome UX Report field data. Its 2025 SEO chapter shows that the basics are nearly universal, but several important signals are still missing on roughly a third of pages.
View the data
| Value | |
|---|---|
| Title tag | 98.5% |
| Meta viewport | 95.2% |
| HTTPS | 91.5% |
| Robots.txt returns 200 | 84.9% |
| H1 heading | 70% |
| Meta description | 67.2% |
| Canonical tag | 67% |
Source: HTTP Archive, Web Almanac 2025, SEO chapter
Two numbers stand out for audits. Only 67% of mobile pages had a canonical tag, and 13.2% of mobile sites returned a 404 for robots.txt. A missing robots.txt is not an error in itself, but it often signals that nobody has decided what crawlers should skip. The same chapter found that 3.02% of mobile sites had canonical tags that changed after JavaScript rendering, which is exactly the kind of conflict a crawl that only reads raw HTML will miss.
Page experience is the bigger gap. In June 2025, fewer than half of mobile pages passed all three Core Web Vitals.
View the data
| Value | |
|---|---|
| CLS 0.1 or less | 81% |
| INP 200 ms or less | 77% |
| LCP 2.5 s or less | 62% |
| All three passed | 48% |
Source: HTTP Archive, Web Almanac 2025, SEO chapter (CrUX data, June 2025)
Largest Contentful Paint is the metric most often failed on mobile, which is why image weight, hero sections and render-blocking app scripts are standard audit findings on Shopify stores. Our guide to Core Web Vitals on Shopify goes deeper.
We'll benchmark your store against your top three competitors on Google and AI answers, flag the technical fixes worth shipping first and show the revenue math behind them.
What deliverables should a technical SEO audit include?
An audit is only as good as what your team can do with it. Ask for these deliverables before you sign anything.
| Deliverable | What it contains | Who uses it |
|---|---|---|
| Executive summary | The 5 to 10 issues that matter most, in plain language, with expected impact | Founders, marketing leads |
| Prioritized issue log | Every finding with affected URLs or templates, severity, effort and owner | SEO and project managers |
| Developer tickets | Reproduction steps, the exact change, acceptance criteria and a source citation | Developers |
| Crawl and indexation data | Exports from the crawl, Search Console and (for larger sites) server logs | Analysts |
| Baseline and measurement plan | Current indexed pages, Core Web Vitals, organic sessions and revenue, plus how each fix will be judged | Everyone |
Google's own guidance on hiring an SEO says an audit "should be about giving you realistic estimates of improvement, and an estimate of the work involved." If a report has neither, it is a crawl export, not an audit.
How a technical SEO audit works, step by step
Most audits follow the same sequence, whether a freelancer or an agency runs them. Timelines depend on site size and access.
- Agree on goals and scope. Name the revenue pages (top collections, best-selling products, key landing pages), the domains and subdomains in scope and any known problems such as a recent migration.
- Grant read-only access. Search Console, analytics and, for larger sites, server logs. Google recommends granting only read access to Search Console at the audit stage.
- Crawl the site. Run a full crawl with JavaScript rendering on and off, so raw and rendered HTML can be compared.
- Cross-check with Google's data. Compare the crawl with the Page indexing report, sitemaps (check them with our sitemap checker) and URL Inspection results. Differences between what you link to and what Google indexes are where the biggest problems hide.
- Review field performance. Pull Core Web Vitals field data by template (home, collection, product, blog) and device.
- Diagnose root causes. Group findings by template or system, not by URL. One collection template bug can explain thousands of flagged pages.
- Prioritize. Score each issue on impact (traffic and revenue at stake), effort and risk, and cite the official documentation behind each recommendation.
- Hand off and verify. Turn the top issues into tickets, ship them, then validate fixes in Search Console and recrawl to confirm.
Our Search Console analyzer is a quick way to find pages losing clicks before you start, and the SEO checker handles single-page spot checks.
How much does a technical SEO audit cost?
There is no reliable, independent price survey for technical audits specifically. The most transparent pricing data we could find is Ahrefs' SEO pricing survey of 439 SEO service providers (updated August 15, 2024). It covers SEO projects in general, not just audits, so treat it as context rather than a quote. In that survey, $2,501 to $5,000 was the most common per-project fee (21.2% of respondents), and 60.6% of respondents charged $1,001 or more per project.
The same survey points to the main drivers of price:
| Cost driver | What Ahrefs found | What it means for an audit |
|---|---|---|
| Provider type | Most common per-project fee: $101 to $250 for freelancers, $2,501 to $5,000 for agencies and $5,001 to $10,000 for consultants | You are paying for depth of analysis and who turns it into tickets |
| Experience | Estimated average per-project fees rose from about $1,882 for providers with 2 years or less to about $9,087 for those with 5 to 10 years | Senior auditors spend more time on diagnosis and prioritization |
| Market served | Providers serving worldwide markets averaged about $8,057 per project vs. about $5,724 for local providers | International sites with hreflang and multiple domains cost more to audit |
| Region | 93.75% of India-based respondents charged $1,500 or less per project | Location changes price, but check whether the work includes implementation support |
Beyond the survey, scope drives cost: the number of URLs and templates, whether log file analysis is included, how many domains or languages are in scope, and whether the provider stays on to help implement fixes. Ahrefs' averages assume each respondent charges the top of their price bracket, so read them as rough estimates.
The free $100M AI Visibility Roadmap, built from 7,960 live pages and 197 A/B tests, shows how to get cited by ChatGPT, Google AI Overviews and Perplexity.
Who should run your technical SEO audit?
Google's advice is that small businesses can often do much of their SEO themselves, starting with its SEO starter guide. For an e-commerce store with thousands of URLs, apps and custom templates, the choice is usually between an in-house team, a freelancer and an agency.
Questions to ask, from Google's own list
- Can you show me examples of previous work and success stories?
- Do you follow Google Search Essentials?
- What results do you expect, in what timeframe, and how do you measure success?
- What's your experience in my industry?
- Will you share every change you make and the reasoning behind your recommendations?
Google adds a few red flags worth repeating: no one can guarantee a #1 ranking, be wary of unsolicited audit offers by email, and ask whether recommendations cite official Google documentation.
Matching the provider to the store
A small store on a standard theme with few apps can often handle a crawl and Search Console review in-house. A store with large catalogs, heavy faceted navigation, a recent migration or international domains benefits from a team that can audit and implement, because most of the value sits in the fixes. That is the model behind our technical SEO services: QCK builds on Shopify (its specialty), WooCommerce and WordPress in-house, and every role, from developers to data analysts, is on the team rather than outsourced.
Why most technical SEO audits never get fixed
The failure point is rarely the diagnosis. It is the handoff. Reports written for SEO specialists list hundreds of warnings at equal weight, developers can't tell which ones matter, and leadership can't see the revenue at stake. The fix is a prioritization model everyone can read.
| Priority | Impact | Effort | Store example |
|---|---|---|---|
| Fix now | High | Low | A robots.txt rule blocking a revenue collection, or a noindex left on product templates after a launch |
| Plan this quarter | High | High | Rebuilding faceted navigation so filtered URLs stop competing with core collections |
| Batch together | Low | Low | Broken internal links, missing alt text and redirect chains |
| Deprioritize | Low | High | Chasing a perfect crawler score on pages with no search demand |
Tie every high-priority item to the pages that earn money. A canonical error on a collection that drives a large share of organic revenue is worth more than a hundred warnings on old blog tags.
How often should you run one, and what comes next?
Run a full technical audit before and after any migration, redesign or theme change, when organic traffic drops without an obvious cause and at least once a year for an active store. Between audits, monitor the Page indexing report and Core Web Vitals monthly so problems are caught early.
Your next step is simple: list your top revenue pages, confirm they are crawlable, indexed and canonical, and work outward from there with the technical SEO audit checklist. If you'd rather have a team audit and implement the fixes, talk to us about your store.
Book a free 30-minute call. We'll review your top pages, prioritize the fixes and show which pages are ready to move.
