12-Point Technical SEO Audit Checklist for 2026

A technical SEO audit checklist is the ordered set of fetches and index checks you run before you argue about copy. Best site crawler debates (Screaming Frog vs Sitebulb vs Lumar, plus OnCrawl, Botify, Semrush, and Ahrefs) are downstream of that list. If you cannot tick the twelve checks below, you do not have a crawler problem. You have an unfinished audit. Google Search Central states that crawling after a recrawl request can take anywhere from a few days to a few weeks, and that requesting a crawl does not guarantee inclusion, according to Google Search Central (2026) (documentation last updated 2025-12-10). That range is why “we requested indexing” is not a line on this checklist.

TL;DR: run Frog or Sitebulb if a person will live in a desktop crawl; run Lumar, OnCrawl, or Botify if you need logs, scheduling, and a platform; keep Ahrefs or Semrush as the suite that also crawls; keep Search Console at $0 as the index log. Do not buy enterprise log analysis for a 400-URL brochure site.

Audits die in the gap between “we crawled” and “we recrawled.” Checks 1–11 without check 12 are a slideshow. The person who owns robots must be in the room when orphans are discussed or you will file tickets into a void. The person who owns the sitemap must be in the room when GSC coverage is discussed or you will submit ghosts. If those two people are you, Frog on a laptop is enough. If they are a platform team with log files, Lumar or Botify is the product and Frog is a spot-check. Semrush and Ahrefs are what you already pay when the suite is the system of record; they do not retire check 12.

BEST_OF earn rate: 15.2% according to first-party mix-config (2026) on 12,514 live pages counted 2026-08-24 (28-day GSC window 2026-07-25 to 2026-08-21). This industry uses the neutral default 10, not a vertical earn rate.

The 12 checks

Twelve is enough. Adding a thirteenth “AI Overviews” line belongs on the surface-split page, not here. For index share and orphans, keep why 48% of pages never got indexed, how 1,400 orphan pages were fixed, and how to reduce time to index as the narrative companions.

Which crawler owns which job

Screaming Frog — best fit: practitioners who want 300+ issue types, custom extraction, and a licence they can renew without a sales cycle. Limitations: desktop, free cap 500 URLs, steep on huge sites. Implementation: paid licence, schedule if you must, export. Primary evidence: Screaming Frog. Screaming Frog paid licence: £199/yr according to Screaming Frog (2026), 500-URL free cap.

Sitebulb — best fit: people who must hand a stakeholder hints, not a raw CSV. Limitations: not a backlink index; URL caps by tier. Implementation: desktop or cloud, export hints. Primary evidence: Sitebulb. Skip if Frog plus a human already writes the narrative. Hint export is 1 narrative per crawl according to Sitebulb, which is the reason to pick it over a raw Frog CSV when a VP will not read 14,000 rows.

Lumar — best fit: enterprise scheduled crawls, log file analysis, crawl-budget control. Limitations: contact vendor; overkill for small sites. Implementation: platform kickoff, log ingest. Primary evidence: Lumar. Skip for a brochure site.

OnCrawl — best fit: log-plus-crawl platforms that already sit in European/enterprise stacks. Limitations: contact vendor. Implementation: connect logs, segment. Primary evidence: OnCrawl. Skip if Lumar or Botify is already in procurement.

Botify — best fit: large sites that want crawl budget and log intelligence as a platform. Limitations: contact vendor; not a $199 desktop tool. Implementation: contracted crawl. Primary evidence: Botify. Skip if you will not ingest logs.

Semrush — best fit: teams that already live in the suite and need a site audit next to keywords. Limitations: not Frog-depth extraction. Implementation: Site Audit in the project. Primary evidence: Semrush. Semrush Pro list price: $139.95/mo according to New Standard Digital (2026).

Ahrefs — best fit: teams that want Site Audit next to a backlink index. Limitations: crawl credits are a budget. Implementation: Lite at $129/mo with 100,000 credits, according to Ahrefs (2026). Skip buying Ahrefs only to avoid Frog.

Who should choose which: Frog or Sitebulb for a human-driven audit. Lumar / OnCrawl / Botify when logs and schedule are the product. Semrush or Ahrefs when the suite is already the system of record and the audit is a module.

Weighted buy

Zero the log-file row if you do not have logs. That is how Frog beats Botify on a 2,000-URL site without anyone being “wrong.”

Feature matrix

Sitebulb desktop about $18–42/mo (Lite about $165/yr) is the June 2026 snapshot according to New Standard Digital (2026). Confirm checkout. Search Console stays $0 as the index log — do not treat it as a crawler.

Twelve-month TCO

Recipe: 14,000 URLs, 1,400 orphans, Indexability

A publisher crawled 14,000 HTML URLs in Frog. inspectionResult.indexStatusResult.coverageState was “crawled – currently not indexed” on a sample that matched 2,200 blocked or canonicalized URLs and 1,400 orphans with 0 inlinks. They spent 18 hours on checks 1–7 before anyone opened a title doc. Three figures and a real field: 14,000 URLs, 1,400 orphans, 2,200 non-indexable, inspectionResult.indexStatusResult.coverageState. Recrawl (check 12) was scheduled 14 days later because Google’s recrawl window is days to weeks, not an afternoon.

A proposed US Tech Automations design would take the Frog export, open a review object per failed check number, and refuse to mark the audit closed until check 12 (recrawl) has a timestamp. n8n, Make, or Zapier can drop the CSV, retry the ticket POST, and keep a run history. You own idempotency (one ticket per URL per check), who may change robots, retention of crawl files, and the person who notices the schedule died.

Who this is for

In-house SEO and agencies who can run a crawl, verify GSC, and change templates. You have more URLs than a spreadsheet of titles.

Red flags: you want a vendor to “request indexing” as the audit; you cannot recrawl; you have no CMS access; you will buy Botify for a 200-URL site.

Key Takeaways

• Twelve checks, then a recrawl; requesting indexing is not a check.

• Frog is the desktop default; Sitebulb is the narrative default; Lumar/OnCrawl/Botify are log platforms.

• Ahrefs and Semrush are suites with an audit module, not log replacements.

• '7 Best' title earn rate: 25.5% according to first-party mix-config (2026) versus 14.0% for “5 Best” — this checklist is 12 points on purpose.

• GSC is the index log at $0; it does not replace a crawler.

• DIY can ticket failed checks; it cannot skip recrawl.

Frequently asked questions

What tools belong on a technical SEO audit in 2026?

A crawler (Frog or Sitebulb at human scale; Lumar, OnCrawl, or Botify at log scale), Search Console, and optionally Ahrefs or Semrush if the suite is already paid. PageSpeed Insights for template vitals. Not a title generator.

Is Screaming Frog better than Sitebulb?

Frog is better for extraction, rendering, and a cheap unlimited-on-desktop licence. Sitebulb is better when the deliverable is explained hints. Many people own Frog and write the narrative themselves.

When do I need Lumar, OnCrawl, or Botify?

When crawl budget and log files are the job: large hostnames, JS-heavy templates, scheduled crawls you cannot babysit. Not when you have 400 URLs and a laptop.

How soon after a recrawl request will Google recrawl?

Google Search Central says a few days to a few weeks, with no guarantee of indexation. Plan check 12 on that window. Do not invent a 24-hour SLA.

When NOT to use US Tech Automations?

Skip it when a weekly Frog crawl plus a sheet already ticks all twelve checks, when Lumar already schedules the recrawl, or when Ahrefs Site Audit plus a developer already closes robots issues. A queue on top of a solved crawl is a second project.

What about Zapier, Make, or n8n?

They can watch a folder for CSV drops, open tickets, retry, and store evidence. They will not run Frog for you unless you schedule the desktop or a cloud crawler. A proposed US Tech Automations design would require check 12 as a closing object and still hold CMS writes for a human.

Close the checklist, then talk about a queue

A 90-day audit sequence should close check 12 before anyone argues about titles. Days 1–15: run Frog or Sitebulb on the hostname, tick checks 1–7 (hosts, robots, canonicals, status codes, redirects, sitemap vs indexability, orphans), and export the 14,000-URL example as a CSV. Days 16–40: fix the 1,400 orphans and the 2,200 non-indexable URLs, then request recrawl knowing Google’s window is days to weeks with no guarantee of inclusion. Days 41–70: recrawl (check 12), compare inspectionResult.indexStatusResult.coverageState on a money-URL sample, and only then open a title doc. Days 71–90: decide whether desktop Frog at £199/yr is enough or whether logs force Lumar, OnCrawl, or Botify. Teams that “request indexing” as the audit skip the list.

The buy is a crawler that can complete all 12 checks, not a prettier UI that skips orphans. Zero the log-file row if you do not have logs: that is how Frog beats Botify on a 2,000-URL site without anyone being wrong. Semrush Pro at $139.95/mo and Ahrefs Lite at $129/mo are suites with an audit module. They do not retire GSC at $0 or check 12. Sitebulb’s desktop snapshot in the June 2026 NSD table is a hint layer. BEST_OF pages earned 15.2% in the 12,514-page count; this industry still uses the neutral default 10. The checklist is 12 points on purpose, not a “7 Best crawlers” trophy.

n8n, Make, or Zapier can watch a folder for CSV drops, open tickets, retry, and store evidence. They will not run Frog unless you schedule the desktop or a cloud crawler. Skip a queue when a weekly Frog crawl plus a sheet already ticks all twelve checks, when Lumar already schedules the recrawl, or when Ahrefs Site Audit plus a developer already closes robots issues. A queue on top of a solved crawl is a second project.

Run the twelve checks in order on the 14,000-URL example so you do not start in the title doc. Check 1: one hostname, HTTPS, www policy. Check 2: robots and meta robots must not noindex a money URL. Check 3: canonical hint matches the live URL Google kept. Check 4: no 4xx/5xx on linked URLs. Check 5: redirect chains stay at 2 or fewer, no loops. Check 6: the sitemap is not a list of noindex URLs or orphans. Check 7: money URLs have more than 0 inlinks — that is the 1,400-orphan bucket. Check 8: near-duplicate templates. Check 9: title and canonical exist in the first HTML, not only after JS. Check 10: field Core Web Vitals on templates. Check 11: hreflang return tags if you have language folders. Check 12: a second crawl after fixes, scheduled 14 days later because Google’s recrawl window is days to weeks. Eighteen hours on checks 1–7 before a title meeting is the discipline. Requesting indexing is not a line on this list.

Lumar, OnCrawl, and Botify exist for log files and scheduled crawls you cannot babysit. They are contact-vendor platforms. A 400-URL brochure site does not need them. Frog’s paid licence is £199/yr with a 500-URL free cap; Sitebulb is the hint layer when a VP will not read the CSV. Semrush Pro at $139.95/mo and Ahrefs Lite at $129/mo ($1,548 over 12 months) sit beside, not instead. Keep Search Console at $0 as the index log. If you cannot recrawl, you do not have an audit. If you cannot change robots, you do not have an audit. If the deliverable is “we requested indexing,” you have a slideshow.

Run the twelve checks, pick Frog or a log platform by scale, recrawl, then decide if a queue should sit on the export. US Tech Automations is that proposed queue — failed check in, review object out. See agentic workflows for the shape and pricing if you need the SKU. The homepage orients the rest.