DIY SEO Audit: A Free 60-Minute Website Performance Check
Six free tools, nine timed steps and Google's own pass thresholds. Find what blocks your rankings in one hour.

Six free tools, nine timed steps and Google's own pass thresholds. Find what blocks your rankings in one hour.

01A DIY SEO audit needs only free tools: Google Search Console, PageSpeed Insights, the Rich Results Test, Screaming Frog free, Bing Webmaster Tools and GA4.
02Google rates a page “good” on Core Web Vitals when LCP is 2.5 seconds or less, INP is 200ms or less and CLS is 0.1 or less at the 75th percentile.
03Screaming Frog SEO Spider’s free version crawls up to 500 URLs per crawl, enough for most small business websites.
04Search Console field data outranks the Lighthouse lab score in a website performance audit, because field data reflects real Chrome users over 28 days.
A DIY SEO audit takes 60 minutes and costs nothing if you stick to six free tools: Google Search Console, PageSpeed Insights, the Rich Results Test, Screaming Frog’s free tier, Bing Webmaster Tools and GA4. Run the steps below in order and you will know which pages Google cannot index, which pages fail Core Web Vitals and which on-page errors to fix first.
This is the same order an agency follows, minus the paid crawlers and the 40-slide deck. Keep a spreadsheet open and log every failed check.
A DIY SEO audit is a structured check of your own site’s indexing, speed, on-page tags and structured data, run with free tools instead of an agency. You need owner access to Google Search Console and GA4, a laptop that can run Screaming Frog, a Bing Webmaster Tools account and one uninterrupted hour.
If any of those terms are new, start with our complete guide to SEO and come back. Everyone else, open these tabs now.
Here is every check in one place. The “Pass threshold” column is what good looks like, taken from Google’s and Screaming Frog’s own documentation. Anything that misses the threshold goes on your fix list.
| Check | Free tool | Where to click | Pass threshold |
|---|---|---|---|
| Penalties | Search Console | Security & Manual Actions > Manual actions | Green check, zero actions |
| Indexing | Search Console | Indexing > Pages | No “Website” source errors on pages you want ranked |
| Key page status | Search Console | Inspect bar at the top > Test live URL | “URL is on Google”, canonical matches yours |
| Sitemap | Search Console | Indexing > Sitemaps | Status Success, under 50,000 URLs and 50MB per file |
| Core Web Vitals (field) | Search Console | Experience > Core Web Vitals | LCP 2.5s or less, INP 200ms or less, CLS 0.1 or less |
| Lab performance | PageSpeed Insights | Paste URL > Analyze > Mobile tab | Lighthouse score 90 or above |
| Titles and descriptions | Screaming Frog (free) | Page Titles and Meta Description tabs | No Missing or Duplicate; titles under 60 characters |
| Broken links | Screaming Frog (free) | Response Codes > Client Error (4xx) | Zero internal 4xx and 5xx |
| Structured data | Rich Results Test | Enter URL > Test URL | Eligible items detected, no errors |
| Second opinion | Bing Webmaster Tools | Site Scan, then start a scan | No Errors; Warnings reviewed |
| Traffic priority | GA4 | Reports > Engagement > Pages and screens | Top 20 pages identified for fixes |

Follow the time boxes. When a step overruns, log the problem and move on: the goal of the first pass is a complete list, not a finished fix.
In Search Console, open Security & Manual Actions, then Manual actions. Google’s help page says a site with no manual action shows a green check mark. If you see an action, stop the audit. Fix every affected page first, because Google says partial fixes do not earn partial restoration, then click Request Review.
Go to Indexing, then Pages. Filter mentally by the Source column: Google’s help page says issues with the source “Website” are generally the ones you can fix. Prioritise these reasons:
Ignore “Duplicate without user-selected canonical” unless the wrong page is winning. Google’s help page calls this working as intended. Note that the example list caps at 1,000 URLs, so large sites should filter by sitemap.
Paste your home page and four best commercial URLs into the inspection bar at the top of Search Console. Check three fields: overall status, “Indexing allowed?” and Google-selected canonical versus user-declared canonical. Then click Test live URL to confirm the live page is indexable.
Pro tip: Search Console caps inspections and index requests per property per day. Spend them on revenue pages and submit a fresh sitemap for everything else.
Open Indexing, then Sitemaps. The status should read Success. Google’s documentation limits each sitemap to 50,000 URLs or 50MB uncompressed, and recommends a Sitemap line with the full URL in robots.txt. Visit yoursite.com/robots.txt and confirm it is there.
Go to Experience, then Core Web Vitals, and open the Mobile report first. Search Console groups similar URLs and labels each group by its worst metric. A new or low-traffic site may show “No data available”, which simply means the Chrome UX Report has too few visits. Skip to Step 6 if so.
Test one URL per template: home, a category or service page, and a blog post. Read the top section (field data from real Chrome users over 28 days) before the Lighthouse score below it. Fix ideas for WordPress sites are in our WordPress speed guide.
Download the SEO Spider, paste your domain into the top bar and click Start. The free version stops at 500 URLs per crawl, enough for most SMB sites. When it finishes, work through these filters:
Google recommends starting with the Rich Results Test. Paste a product, article or FAQ URL and confirm it detects valid items. Then start a Site Scan in Bing Webmaster Tools, which sorts issues into Errors, Warnings and Notices. Review the Errors first once the scan completes.
Watch out: Cloudflare’s documentation says its managed WAF rule can block Bing Site Scan as a fake Bingbot. Add a temporary skip exception, run the scan, then delete the exception.
Open Reports, then Engagement, then Pages and screens. Sort by Views and mark your top 20 pages. Any of those pages that appeared in Steps 2 to 8 go to the top of the fix list. Our GA4 guide explains the setup if the report looks empty.

A good website performance audit result means real users on mobile hit LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less at the 75th percentile, with a Lighthouse score of 90 or above as the lab backup. Field data always outranks the lab score.
Google’s Search Console help page sets the bands. Needs improvement runs up to 4 seconds for LCP, 500ms for INP and 0.25 for CLS. Anything worse is Poor. INP replaced First Input Delay as a Core Web Vital in 2024, so ignore old audits that still grade FID.
Lab and field numbers often disagree. Google’s PageSpeed Insights documentation explains that Lighthouse simulates one mid-tier phone on a fixed network, while field data reflects thousands of real devices. A 95 Lighthouse score with a failing field LCP is still a fail.
Your Lighthouse score is a rehearsal. Your Core Web Vitals field data is the actual show.
Fix problems that block indexing first, then problems on high-traffic pages, then sitewide template issues, then everything else. A noindex tag on a product page costs more than a hundred long meta descriptions, so sort your list by impact, not by how many rows a tool reports.
PingTalks uses a simple four-tier triage on every audit:
After a fix, return to the Page indexing issue and click Validate fix. Google’s help page says validation typically takes up to about two weeks.
Run the full 60-minute DIY SEO audit once a quarter and after any redesign, migration or plugin overhaul. Check the Page indexing and Core Web Vitals reports monthly, since both update from live data and catch regressions long before rankings drop.
Search Console can also tell you more than most marketers ask of it. Our list of Search Console features marketers never use is a good next read once this audit is done.
For a site under 500 URLs, this free stack covers almost everything a paid audit tool would flag. Pay for a crawler only when you outgrow Screaming Frog’s free limit or need JavaScript rendering, which the free version restricts. Until then, the bottleneck is fixing, not finding.
Yes. Google Search Console, PageSpeed Insights, the Rich Results Test, Bing Webmaster Tools and GA4 are free, and Screaming Frog SEO Spider is free up to 500 URLs per crawl. That stack covers indexing, speed, on-page tags and structured data for most small sites.
PageSpeed Insights tests one URL and shows both Lighthouse lab data and real-user field data. The Core Web Vitals report in Search Console groups similar URLs across your whole site using Chrome UX Report field data. Use the report to find problem groups and PageSpeed Insights to diagnose one page.
The report needs enough real Chrome visits for a URL group before it shows data. New properties can show “No data available” for a few days, and low-traffic sites may never qualify. Use PageSpeed Insights lab data in the meantime.
No. Lighthouse is lab data from one simulated device, while Core Web Vitals are judged on real-user field data at the 75th percentile. A page can score 90 in Lighthouse and still fail field LCP or INP.
Google’s Page indexing help page says validation typically takes up to about two weeks. Do not click Validate fix again while a validation is running. If it fails, fix the reported URLs and start a new validation.
The paid licence removes the 500 URL crawl limit and unlocks features the free version restricts, such as saving crawls, crawl configuration, JavaScript rendering and custom extraction. Screaming Frog lists it at 199 GBP per year.
What changed in marketing and AI, why it matters and exactly what to do. In your inbox at 11:00 IST.