Guide
A content audit that ends in a decision, not a spreadsheet
Most audits produce rows nobody acts on. This is the shorter version: pull what your sitemap and Search Console already know, find the queries you are missing and the pages that are not earning, and fix the few that matter first.
Reads your existing sitemap116 languages
What a content audit is for
Not an inventory of what exists — a decision about what to write, retarget or leave alone.
- It starts from demand, not from your pages
- A useful audit answers one question per query: does a page of ours answer this, is it good enough to, or is nobody answering it at all?
- Its output is a queue
- Every finding ends as one of three instructions — write this, retarget that, leave it. A finding with no instruction attached is a row, not an audit.
- It is never one pass
- Pages decay, queries shift, and new posts publish every week. An audit that is a project rather than a habit is out of date the month it finishes.
What to pull, in this order
Three sources, roughly an hour of work, and no crawling tools.
- 01
Your sitemap
Every page you have published, with its last-modified date. That is the inventory — the part an audit tool spends the most time collecting and the least time deciding about.
- 02
Search Console: queries and pages
Sixteen months of queries with impressions, clicks and average position, and the pages they landed on. This is the only source that says what Google already thinks each page is for.
- 03
The gap between the two
Queries with impressions but no page that answers them are the cheapest work in SEO: Google has already shown interest, and there is nothing for the reader to click.
The four findings that matter
Everything else in a 400-row sheet is a consequence of one of these.
- Queries you appear for but do not answer
- Impressions with no matching page: you turned up in the results, the reader found nothing about it, and they went back. Write the page.
- Pages just below the first page
- Positions on the second and third page for a query the page is clearly about. These move with title, metadata and internal links far more reliably than a brand-new post ranks at all.
- Impressions without clicks
- The page is being shown and not chosen. That is a title and snippet problem, not a ranking problem — and rewriting a description is cheaper than writing an article.
- Pages that used to earn and no longer do
- Decay is usually a competitor or an intent shift, not a penalty. Look at what ranks for that query now before rewriting anything.
What to do with each finding
One action per finding. A finding with no action belongs in the inventory, not in the queue.
What you found
- Impressions for a query with no page behind them
- A page sitting at position 8 for its own topic
- High impressions, few clicks for that position
- A page that lost half its clicks in three months
What to do
- Write it — one post, the query as the promise of the title, a date in the calendar
- Retarget it — title and metadata aimed at the query it already earns for, same URL
- Rewrite the snippet — same page, new description, a title that does not read like its neighbour's
- Check the SERP first — if the intent changed, the page needs a different job, not a rewrite
The part worth automating
The judgement is yours. The recurring collection, dating and linking is not.
- Reading the sitemap and Search Console every week, so the audit is never a project you restart from scratch.
- Choosing the queries worth going after, per site and per language, instead of one shared topic list.
- Dating the work — every post committed to a day — so the plan becomes publishing rather than a backlog.
- Re-reading a post two weeks after it publishes, while the evidence is fresh, instead of finding the decay a year later.
Questions about auditing content
The short answers, in the order they come up.
Do you need Search Console for a content audit?
For a good one, yes. Your sitemap says what exists; Search Console says which queries each page is actually being shown for, how many impressions it earns and where it sits. Without it, an audit can only judge a page against its own promise.
What is the difference between a content audit and a content inventory?
An inventory lists what you have. An audit adds a decision to each line: write, retarget, or leave it alone. If the output is a spreadsheet with no instructions in it, you have an inventory.
How often should a content audit run?
Continuously, in small passes, rather than once a year in one large one. Pages decay and queries move every month, and an annual audit is out of date before it is finished.
Can a content audit be automated?
The collection can be, and so can the dating and the internal linking. The judgement — whether a query deserves a page, and whether what you already have answers it — is the part worth keeping.
How big should a content audit be?
Big enough to cover the queries you are already being shown for, and no bigger for the first pass. Start with the pages that earn impressions and the queries with none, and let the long tail wait: a 400-row sheet nobody finishes is worse than a 20-row queue you empty.
Should you delete the pages an audit finds to be dead?
Rarely as the first move. A page earning nothing may still be holding a link, a redirect target, or a query worth keeping: rewrite it, merge it into the page that should answer that query, or redirect it — and only then consider removing it.
Mais sobre conteúdo
- Automação de conteúdo SEO
Automação de blog: o que corre sem supervisão, onde para, o que recusa fazer.
- Publicar mais artigos
Quatro formas de aumentar a produção, e o modo de falha de cada uma.
Skip the spreadsheet
See what your sitemap is missing.
The scan is free and needs no signup: it reads your sitemap and Search Console and shows which queries your site does not answer yet, before you decide anything — and it does not guarantee a position, because nobody controls the index.
Findings per site and language20€ per site, per language, per month3 dias grátis, sem cartão