You can audit your own site in about an hour with free tools, as long as the site is small: somewhere between a few dozen and a few hundred pages. All you need is Google Search Console, PageSpeed Insights and a Google search.
What you get from that hour is a first pass. It catches the problems that stop pages being indexed, found or usable, and it ends with a short list of fixes in priority order. It won't review every article for quality, and on a site with thousands of URLs the same steps take a day or more.
Before the timer starts, check that your site is verified in Search Console and has been for a few weeks, because a brand-new property has almost nothing to show. Then open a blank note with three headings: Fix this week, Schedule, Ignore. Everything you find goes under one of them.
The hour at a glance
| Minutes | Where | What you're checking |
|---|---|---|
| 0β5 | Google site: search | What Google shows for your domain |
| 5β20 | Page indexing report | Pages that aren't indexed, and why |
| 20β30 | Performance report | Pages losing clicks, near-miss rankings |
| 30β40 | Core Web Vitals, PageSpeed Insights | Speed on real phones |
| 40β45 | Links report | Important pages with few internal links |
| 45β50 | Five pages, by hand | Titles, headings, dead links |
| 50β60 | Your note | The fix list |
The times are rough. If one step runs over, write down where you stopped and move on, because the last ten minutes matter more than any single check.
Minutes 0β5: search Google for your own site
Type site:yourdomain.com into Google and scroll through a few pages of results.
Look for things that shouldn't be public. Tag and archive pages, internal search results, test posts, a staging copy of the site, URLs with tracking parameters on the end, or pages in a language you never wrote (a common sign of a hacked site). Note each kind once, without listing every URL.
Then read your titles and descriptions the way a searcher would. Truncated titles, the same title on several pages, and results that show only your site name are all worth a line in the note.
Don't rely on the result count. It's an estimate, and the next report gives you the real numbers.
Minutes 5β20: the Page indexing report
In Search Console's left menu, open Pages under the Indexing heading. Google's help calls this the Page indexing report. It shows how many URLs are indexed, how many aren't, and a table headed "Why pages aren't indexed" with a row per reason.
A big "not indexed" number isn't a problem by itself. Google's guide to the report says you shouldn't expect every URL to be indexed, only your canonical pages. So the useful move is to change the filter at the top from all known pages to All submitted pages. Now you're only looking at URLs from your sitemap, which are the pages you asked Google to index. Anything not indexed in that view deserves a look.
Click each reason to see example URLs, then sort them:
| Reason shown | What it means | What to do |
|---|---|---|
| Server error (5xx) | Your server failed when Google asked | Fix this week |
| URL marked 'noindex', or blocked by robots.txt | You told Google to stay out | Urgent if it's a page you want ranked; otherwise ignore |
| Not found (404) | The URL is gone | Redirect it if other pages link to it or it used to get visits; otherwise ignore |
| Soft 404 | The page loads but looks empty or like an error | Add real content, or return a proper 404 |
| Crawled - currently not indexed | Google fetched it and left it out | Check for thin or overlapping content |
| Discovered - currently not indexed | Google knows the URL but hasn't fetched it | Link to it from related pages, then wait |
| Duplicate without user-selected canonical | Google picked another URL as the main one | Set a canonical tag or redirect |
| Alternate page with proper canonical tag, or Page with redirect | Working as intended | Ignore |
"Crawled - currently not indexed" is the one people misread. Google doesn't give a reason for it and says there's no need to resubmit the URL. If the examples are feeds and paginated archives, leave them. If they're articles you care about, open two or three and compare them with what ranks for the same topic. Short pages and pages that repeat another post on your site are the usual suspects.
While you're in this part of the menu, open Sitemaps and confirm your sitemap is listed and was read without errors.
Minutes 20β30: the Performance report
Open the Performance report. By default it shows clicks and impressions for the last three months. Tick Average CTR and Average position above the chart so all four metrics appear.
First, find what's slipping. Click the date filter, choose the Compare tab, and compare the last three months with the previous period. Go to the Pages tab and sort by clicks difference. The pages at the top of the losses are your candidates for an update. A seasonal topic will show a drop that isn't a fault, so check the 16-month view before blaming the page.
Second, find near misses. On the Queries tab, sort by impressions and look for searches where your average position sits just off the first page. Those pages already have Google's attention, so improving them usually pays back faster than writing something new. Write down three at most.
Third, click any query that matters to you and switch to the Pages tab. If two of your URLs show up for the same search, they may be competing with each other. Note the pair so you can merge them or make each one clearly about a different thing, which is the same thinking behind grouping a small site's articles into topic clusters.