Technical SEO Audit: 7 Ecommerce Store Fixes 2026

A technical SEO audit for an ecommerce store is a crawl-plus-index check that lists which SKU, collection, facet, and pagination URLs search engines can fetch, render, and keep — and which ones waste crawl budget. It is not a content grade, it is not a paid-media audit, and it is not a merchandising review. This page compares seven audit tools — Botify, Lumar, Ryte, Screaming Frog, Sitebulb, Semrush, and Ahrefs — and puts US Tech Automations above them as the ticket layer that blocks a recrawl request when Status Code, canonical, and noindex still disagree.

TL;DR: Buy Screaming Frog when a desktop crawl of the SKU template is the job and $279/year is enough. Buy Sitebulb when the auditor wants visualized crawl graphs on the same machine. Buy Botify or Lumar when log files and crawl-budget modeling have to run every week on a catalog that a laptop crawl will not finish. Buy Semrush or Ahrefs Site Audit when the team already lives in that suite and the catalog is not huge. Do not treat a recrawl request as an index guarantee.

What a technical SEO audit actually is

On a store, the audit has to answer seven questions: which templates return 200, which facets are indexable, which canonicals point at the right SKU, which paginated collections are reachable, which JS-rendered prices search bots see, which hreflang pairs exist for each locale, and which log-file hits are Googlebot versus wasted parameter crawls. If the report cannot name a template and a status code, it is a content memo.

Ecommerce is not in the counted vertical earn-rate table; treat it as the Neutral vertical default: 10 in the mix-config (12,514-page count, 2026-08-24), not a vertical earn rate. BEST_OF earn rate: 15.2% according to US Tech Automations (12,514 live pages, counted 2026-08-24). That figure is first-party shape, not a vendor rank.

Stores that already compared a grader to a crawler should keep that thread on Semrush vs Surfer for ecommerce stores. Teams coming from a CMS-layer bake-off should start at SEOmatic vs AirOps for ecommerce. Budget owners who need dollars before tools should read ecommerce SEO cost and return here for the crawl.

Key Takeaways

• A store audit is a template-and-status-code job. If the export cannot group 12,000 SKUs by Status Code, you are reading pages, not a catalog.

• Frog paid licence: $279/year according to Screaming Frog (retrieved 2026-09-07). The free build stops at 500 URLs — useless on a real catalog.

• Recrawl is not indexation. Google Search Central states that crawling after a recrawl request can take a few days to a few weeks, and that the request does not guarantee inclusion, in docs last updated 2025-12-10, according to Google Search Central (2025).

• Cloud crawlers (Botify, Lumar, Ryte) win when log files and JS rendering have to run on a schedule. Desktop crawlers (Frog, Sitebulb) win when an auditor can finish the job on a machine they control.

• Zapier, Make, or n8n can retry a 5xx and keep a run history when they POST crawl rows into a sheet. They will not own the indexability threshold, the idempotent URL id, or who is allowed to fire a recrawl.

Who this is for

This page is for ecommerce SEO leads, platform engineers, and agencies who ship collection and SKU templates and need a crawler in the release loop.

Red flags: Skip a paid crawler if you have a handful of SKUs you can click by hand. Skip Botify if you will never load server logs. Skip Ahrefs Site Audit as the only tool if the catalog is JavaScript-rendered and you need log-file proof of Googlebot waste.

Botify vs Lumar for ecommerce

Botify is a log-file and crawl-budget platform. The public site describes real-time log analysis, JS rendering, and crawl-budget modeling aimed at large sites. Public list dollars were not in this page's three-fetch cap, so every Botify price cell reads contact vendor. What the product is for: weekly crawls of catalogs that a laptop will not finish, plus log lines that show Googlebot hitting faceted URLs you meant to noindex.

Lumar (formerly DeepCrawl) is a cloud crawler with scheduled audits, change detection, and Looker-style reporting. Public list dollars also read contact vendor. What the product is for: a team that wants a scheduled crawl in the cloud without installing Frog, and a QA loop that diffs this week's indexable SKU count against last week's.

Neither tool replaces Google Search Console. Neither tool is a merchandising PIM. Pick Botify when logs are the argument you take to engineering. Pick Lumar when the SEO team wants a scheduled cloud crawl and a ticket export without owning a log pipeline. Pick neither if 8,000 URLs on Frog already covers the catalog.

Ryte sits in the same cloud-audit band with a European footprint and a site-quality score. Sitebulb is the desktop visualizer: crawl graphs, hints, and a local project file. Semrush and Ahrefs Site Audit are suite modules; they are good enough when the catalog is modest and the team already pays for the suite.

Evaluation criteria for store crawls

Weight log-file access and template grouping over "number of issues found." A crawler that dumps 40,000 duplicate-title warnings without grouping them by collection template is noise.

Source: Screaming Frog, Ahrefs pricing, Semrush pricing, retrieved 2026-09-07. Botify, Lumar, Ryte, Sitebulb were not in the fetch cap.

Ahrefs Lite includes Ahrefs crawl credits: 100,000/mo according to Ahrefs (retrieved 2026-09-07) and a 25,000 page cap per project. That is enough for a mid-size catalog and not enough for a marketplace with faceted crawl traps.

Ahrefs Lite: $129/mo according to Ahrefs (retrieved 2026-09-07) is the adjacent research seat, not a log-file platform.

Semrush's SEO plan monitors 5 websites at Semrush SEO plan: $139/mo according to Semrush (retrieved 2026-09-07).

Recrawl windows and crawl budget

The audit is not finished when the crawler stops. Someone still has to decide which URLs to request a recrawl on, and someone has to accept that Google may not recrawl them this week. Search Central's recrawl document, last updated 2025-12-10, is explicit: the wait is days to weeks, and inclusion is not guaranteed. A store that ships 400 new SKUs on a Monday and hammers URL Inspection on all 400 is spending quota, not buying indexation.

Crawl budget on ecommerce is usually wasted on filters (?color=, ?sort=), search-result URLs, and stale paginated collections. The fix is robots.txt, canonicals, and noindex on the junk templates — not a bigger Botify crawl that simply discovers more junk. Log files are how you prove Googlebot is in the trap. Frog will not give you logs. Botify will.

Vendor profiles

Botify — best fit. Log-file proof that Googlebot is burning budget on facets, plus a cloud crawl that a laptop cannot finish. Limitations: you still need engineering to close the robots.txt and canonical tickets; public dollars are contact vendor. Implementation: connect logs, segment SKU vs collection vs facet, export the waste URLs. Primary evidence: Botify.

Lumar — best fit. Scheduled cloud crawls and change detection for a team that will not install Frog. Limitations: without logs you are inferring budget, not measuring it. Primary evidence: Lumar.

Ryte — best fit. Site-quality monitoring for teams that want a European cloud auditor and a scoreboard. Limitations: not a substitute for log-file analysis on a facet-heavy catalog. Primary evidence: Ryte.

Screaming Frog — best fit. Desktop crawl of the SKU template, custom extraction of price and availability, GSC and PSI attach, CSV into the ticket. Limitations: no log files; free cap is 500 URLs; paid is $279/year and memory-bound. Primary evidence: Screaming Frog.

Sitebulb — best fit. Visual crawl graphs and hints for auditors who think in diagrams. Limitations: still a desktop project; not a log platform. Primary evidence: Sitebulb.

Semrush Site Audit — best fit. Already-in-suite check for a modest catalog. Limitations: 5 websites on the $139 SEO plan; not a log-file tool. Primary evidence: Semrush.

Ahrefs Site Audit — best fit. Already-in-suite check with 100,000 crawl credits on Lite at $129/mo. Limitations: 25,000 pages per project on Lite; not logs. Primary evidence: Ahrefs.

A store audit recipe

1. List templates: SKU, collection, facet, search, pagination, locale.

2. Crawl the production host in Frog paid (or Botify if logs are the argument).

3. Group the export by template and Status Code.

4. Fail any SKU template row that is 200 + indexable + duplicate canonical.

5. Close robots.txt and canonical tickets before you request a recrawl.

6. Request recrawl only on the URLs you actually changed.

7. Wait days to weeks. Do not treat silence as success.

Worked example: a Shopify catalog with 12,400 SKUs, 8 collection templates, and 3 locales, shipping a theme change that moved prices into JS. The SEO engineer runs Frog paid at $279/year, sets JS rendering on, and extracts price with XPath. The export shows 1,860 collection-filter URLs returning 200 with no canonical. The engineer groups those rows by Status Code, files one ticket per template (not 1,860 tickets), and blocks URL Inspection until the facet template is noindex. A Shopify products/update webhook can fan out to Make or n8n, retry on 5xx, and keep a run history when a merchant edits a SKU. The store still owns observability, idempotency (one ticket id per template-release), escalation, access controls, retention, and maintenance. A proposed US Tech Automations design would take the same Status Code export, retry on 5xx, and wait for a human to sign the facet noindex before any recrawl fires.

When NOT to use US Tech Automations: skip it when free Frog's 500-URL cap already covers a tiny catalog you can click; skip it when Botify already opens the ticket in Jira and engineering already treats that ticket as the system of record; skip it when the only "audit" you need is one collection URL pasted into Search Console.

The homepage describes the ticket layer. Configure the recrawl gate on pricing if US Tech Automations should own the retry and the human review point.

FAQ

What is a technical SEO audit for ecommerce stores?

A crawl-plus-index check of SKU, collection, facet, and pagination templates that reports which URLs return 200, which are indexable, and which waste crawl budget. It is not a content score and it is not a merchandising review.

What are the best tech SEO audit tools for ecommerce?

Screaming Frog at $279/year for desktop SKU crawls, Sitebulb when you want graphs, Botify or Lumar when you need logs and a cloud schedule, Semrush or Ahrefs Site Audit when the suite is already paid and the catalog is modest.

Is Botify or Lumar better for an ecommerce SEO audit?

Botify is better when server logs have to prove Googlebot waste. Lumar is better when the team wants a scheduled cloud crawl and change detection without owning a log pipeline. Neither replaces GSC.

How long does a recrawl take after I fix a SKU URL?

Google Search Central says crawling after a recrawl request can take a few days to a few weeks, and the request does not guarantee inclusion. Docs last updated 2025-12-10.

Can Zapier or n8n run the audit for us?

They can POST crawl CSVs, retry 5xx, keep run histories, and open tickets. They cannot crawl 12,400 SKUs or read server logs. Someone still owns the indexability threshold and the recrawl button.

Why is the free Screaming Frog build not enough for a store?

The free build stops at 500 URLs. A catalog with 12,400 SKUs plus collections and facets is tens of thousands of URLs. Paid is $279/year and still memory-bound.