Skip to content
Eudora Technology
Home  / Insights
Digital Marketing

A Technical SEO Audit You Can Run in an Afternoon

Helloquence-61189.
Photo: Helloquence-61189 by helloquence, CC0, via Wikimedia Commons

You can do the useful 80% of a technical SEO audit yourself, in one afternoon, with Search Console, PageSpeed Insights and your browser. Three hours, no licence fees, no retainer. The hard part is not finding problems — any crawler will hand you four hundred warnings — it is knowing which numbers are genuinely bad. So this runs in three one-hour blocks, and each one comes with the benchmark figures from the 2025 Web Almanac so you can tell a real fault from a cosmetic one.

Chinese keyboard with fingers
Three hours with free tools finds the faults that matter. A 400-warning crawl report mostly finds work for whoever sold you the crawl.Photo: Keyboard with fingers by Cangjie6, CC BY-SA 4.0, via Wikimedia Commons

The afternoon plan

Block out three hours and work in this order, because each block depends on the one before it. There is no point tuning images on a page Google cannot index.

  1. Hour one — reach and indexing. Can Googlebot fetch your pages, and has it chosen to index them? Search Console’s Pages report and the URL Inspection tool answer both.
  2. Hour two — speed and stability. What do real visitors experience? Search Console’s Core Web Vitals report and PageSpeed Insights, field data only.
  3. Hour three — on-page signals. Titles, headings, alt text, structured data and internal links on your fifteen most important URLs.

Write findings in a single document with three columns: what is wrong, what it costs you, and who can fix it. If the third column is empty, the item is not a finding, it is a complaint.

Hour one: can Google reach and index your pages

Start in Search Console, Indexing, Pages. The chart splits your URLs into indexed and not indexed, and the reasons list underneath is where the real information lives. “Crawled, currently not indexed” usually means Google read the page and judged it not worth storing. “Discovered, currently not indexed” often means a crawl budget or server speed problem. “Excluded by noindex tag” means somebody made a decision, deliberately or not.

Then check your sitemap. Google’s documentation says it supports the formats defined by the sitemaps protocol and has no preference between them, so the format matters far less than the contents. A sitemap listing redirected, noindexed or 404 URLs is actively unhelpful. On WordPress the sitemap is usually generated by your SEO plugin, so the fix is a plugin setting rather than a file edit.

Finish the hour with URL Inspection on five pages: your home page, your most important service page, your best blog post, a page you suspect is broken, and one page you have never thought about. Use “View crawled page” to see the HTML Googlebot actually received. If your main content is missing from that HTML, you have found the most important fault on the site.

Jeff Sheldon 2014-11-18
Check what the crawler received, not what your CMS preview renders. The two are different more often than anyone expects.Photo: Office desk with computer and music player (Unsplash) by Jeff Sheldon ugmonk, CC0, via Wikimedia Commons

robots.txt does not mean hidden

This one causes real damage, so it is worth being precise. Google’s own introduction to robots.txt says the file tells crawlers which URLs they can access, that it is used mainly to avoid overloading a site with requests, and that it is not a mechanism for keeping a web page out of Google. To keep a page out, you block indexing with noindex or you password-protect it.

The failure mode is specific. A URL disallowed in robots.txt can still be indexed if something links to it, because Google never fetches the page and therefore never sees your noindex tag. You end up with a URL in the index and no snippet. If you want a page gone, let Google crawl it and tell it to go away on the page itself.

robots.txt mistakes worth checking for
  • A Disallow: / left behind from a staging site — rare, catastrophic, and takes ten seconds to check.
  • Blocking /wp-content/ or a CSS and JavaScript folder, which stops Google rendering the page as a user sees it.
  • A disallow rule on a page that also carries noindex, so the noindex is never read.
  • Bot-protection or CDN rules blocking Googlebot above the application, which robots.txt will never show you. Test with URL Inspection.

Canonicals, duplicates and parameter sprawl

Canonical tags are the most over-used tool in the box. Google’s canonicalization documentation describes the process as selecting the representative URL for a piece of content, and the help page on specifying a canonical is clear that none of the methods are required — if you do not specify one, Google identifies the version it considers best for users.

So do not spend your hour on canonicals. Spend it on the three duplicates that actually exist on most small sites: the same page reachable with and without a trailing slash, the same page on http and https, and filtered or sorted listing URLs with query parameters generating endless near-identical pages. The first two are redirects. The third is usually a theme or plugin setting.

Use URL Inspection to see which URL Google picked as canonical. If Google’s choice and yours differ, Google is telling you something about how the pages are linked internally. That is more useful than overriding it.

Hour two: Core Web Vitals, measured on real visits

Core Web Vitals are three field metrics, and the thresholds are fixed. web.dev’s explanation of how they were defined sets the pass bar at the 75th percentile: if at least 75% of page views to a site meet the good threshold, the site is classified as good for that metric. Good means Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint within 200 milliseconds, and Cumulative Layout Shift of 0.1 or less.

The 75th percentile matters more than the numbers. It means your average visitor is irrelevant; the slowest quarter decides. A site that feels instant on your office fibre and your two-year-old laptop can still fail, because the measurement includes the visitor on a mid-range Android phone on a train.

In PageSpeed Insights, read the field data at the top and treat the lab score below it as a diagnostic hint only. A green lab score of 98 with failing field data is common and means your real visitors are slower than your test. Only the field data affects Search.

MetricGoodNeeds improvementPoor% desktop good% mobile good
Largest Contentful Paint (LCP)≤ 2.5 s2.5–4.0 s> 4.0 s74%62%
Interaction to Next Paint (INP)≤ 200 ms200–500 ms> 500 ms97%77%
Cumulative Layout Shift (CLS)≤ 0.10.1–0.25> 0.2572%81%
Time to First Byte (TTFB), supporting≤ 0.8 s0.8–1.8 s> 1.8 s55%44%
First Contentful Paint (FCP), supporting≤ 1.8 s1.8–3.0 s> 3.0 s70%55%
Thresholds from web.dev; the share of sites achieving “good” from the Web Almanac 2025 Performance chapter, July 2025 CrUX data. Both listed in Sources.

Two things jump out of that table. Interactivity is almost solved on desktop and clearly not on mobile, a 20-point gap caused by slower phone processors chewing through JavaScript. And layout stability is the one metric where mobile beats desktop, at 81% against 72%, largely because desktop pages have more room for late-loading sidebars and ad slots to shove content around.

Where the web actually sits on each metric

Context stops you panicking. The Web Almanac’s Performance chapter, drawing on CrUX data from July 2025, found that 48% of mobile sites and 56% of desktop sites achieved good scores across all three Core Web Vitals. In 2024 those figures were 44% and 55%, and back in 2021, the first year of the metrics, they were 32% and 41%.

Share of sites with good Core Web Vitals on all three metrics
DesktopMobile
202141%32%
202455%44%
202556%48%
Source: Web Almanac 2025, Performance chapter, HTTP Archive, using Chrome UX Report data. Full reference in Sources.

Popularity does not help. The same chapter reports that among the top 1,000 websites, 59% of desktop sites have good Core Web Vitals against 51% on mobile, and mobile gets worse further down the ranks — 42% for the top 10,000 and 37% for the top 100,000. Big brands ship heavy pages. You are not competing against a perfect web.

One very specific finding is worth acting on today: the Almanac found about 16% of pages still lazy-load their LCP image, which delays the one piece of content the metric is measuring. If your hero image has loading="lazy" on it, remove that attribute and you may fix LCP in a single edit.

If at least 75 percent of page views to a site meet the good threshold, the site is classified as having good performance for that metric.

web.dev, “How the Core Web Vitals metrics thresholds were defined”

Hour three: titles, headings, alt text and markup

The last hour is the cheapest and most often skipped. Take your fifteen most important URLs — home page, service pages, top blog posts — and check five things on each: a unique title under about 60 characters that leads with the thing people search for, a meta description that reads like a reason to click, exactly one non-empty H1, a sensible H2 outline, and alt text on every image that carries information.

The benchmark here is embarrassing in your favour. The 2025 Web Almanac’s SEO chapter found an H1 on 70% of pages but only 66% non-empty, and at the median just 60% of images on mobile pages had alt attributes, up from 58% in 2024. Getting these right on fifteen pages takes an hour and puts you ahead of a large slice of the web.

Structured data goes in the same hour. JSON-LD appeared on 43% of home pages in the 2025 crawl and only 39% of inner pages on desktop, so adding Organization and Article markup is still differentiating. Keep it truthful: markup that does not match the visible page is worse than no markup.

  • Titles — unique, front-loaded, written for a human scanning a results page.
  • One H1 — with words in it. On most content systems this is the post or page title, so check your theme is not adding a second.
  • Alt text — describe the information, not the file. “Rack of network switches with labelled patch cables” beats “IMG_4821”.
  • Internal links — every important page should be reachable in three clicks from the home page, with anchor text that says where it goes.
  • Structured data — Organization once, Article on posts, Breadcrumbs sitewide. Nothing you cannot see on the page.

What to fix first, and what to leave alone

You will finish the afternoon with a list. Fix in this order: anything stopping indexing, then anything a visitor experiences, then anything a crawler merely notices. An accidental noindex outranks a slow image. A slow image outranks a missing canonical.

And here is the part no audit tool will tell you. Leave alone: keyword density, the exact length of your meta descriptions, the handful of 404s from links nobody follows, and every warning about a third-party script you cannot change. Technical SEO has a point of diminishing returns and it arrives sooner than the industry admits.

Once the technical floor is sound, the gains come from content and from choosing where to spend. We cover the content side in content marketing that actually works, the groundwork in SEO fundamentals every business should know, and the budget question in SEO vs paid ads.

This is an image of "African people at work" from
Fix indexing first, visitor experience second, crawler warnings last. The order saves more time than the tooling.Photo: African in a office with a laptop by Minette Lontsie, CC BY-SA 4.0, via Wikimedia Commons
48%
Mobile sites with good Core Web Vitals, 2025
77%
Mobile sites with good INP
66%
Pages with a non-empty H1
16%
Pages that lazy-load their LCP image
Figures from the Web Almanac 2025 Performance and SEO chapters, both listed in Sources.

Frequently asked questions

Do I need a paid crawler like Screaming Frog or Sitebulb?

Not for a site under a few hundred pages. Search Console tells you what Google thinks, which is the opinion that counts, and URL Inspection shows you the crawled HTML. A desktop crawler earns its keep when you have thousands of URLs, heavy faceted navigation or a migration to plan. Buy it when the spreadsheet gets unmanageable, not before.

My PageSpeed score is 95 but Search Console says my pages are poor. Why?

The score is a lab simulation on one synthetic device. Search Console reports field data from real Chrome users at the 75th percentile over a 28-day window. Your real visitors are on slower phones and worse networks than the test. Always trust the field data, and use the lab audit only as a list of things to try.

How long after fixing something should I expect Search Console to change?

Core Web Vitals reports move on a 28-day rolling window, so allow a month before you judge a performance fix. Indexing changes depend on recrawl frequency, which can be days for a busy site and considerably longer for a quiet one. You can request reindexing for individual URLs, but not for the whole site.

Should I worry about every 404 the audit finds?

No. A 404 on a URL nothing links to costs you nothing. What matters is a 404 that an internal link, a sitemap entry or an external backlink points at. Redirect those to the closest useful page. Redirecting everything to the home page is worse than leaving the 404, because it wastes the visitor’s time and tells Google nothing.

Is it worth doing this myself rather than paying for an audit?

Run it yourself first. You will fix half the findings in the same afternoon and you will understand your own site better, which makes any later conversation with an agency much cheaper. Pay for help when the remaining problems need developer time, a server change or a migration plan.

If your afternoon ends with findings that need developer time, we pick up from there remotely — indexing faults, Core Web Vitals work and structured data. Our digital marketing services include a written audit you keep, not a dashboard you rent. Get in touch with Eudora Technology to talk about your project.

Sources

  1. How the Core Web Vitals metrics thresholds were defined web.dev (Google) · updated May 2025
  2. Web Almanac 2025, Performance chapter HTTP Archive · published January 2026, July 2025 crawl
  3. Web Almanac 2025, SEO chapter HTTP Archive · 2025 crawl
  4. Introduction to robots.txt Google Search Central · retrieved April 2026
  5. What is URL canonicalization Google Search Central · retrieved April 2026
  6. Build and submit a sitemap Google Search Central · retrieved April 2026
Keep reading

Related insights