What is an SEO audit? It is a look at the site as it is: what is indexed, what the important pages say, and where the technical and content problems actually sit. You should receive a short list in an order you can act on, not a dump with no sequence. SEO Audits says the same thing. Search Console is one of the places that list comes from, because it shows queries and pages rather than a score. An audit is a map of the current site. It is not a promise about next quarter.
Takeaways
- An audit ends in a prioritized list, not a binder.
- It covers indexation, templates, and the pages that matter commercially.
- Scope the size of the site before the crawl.
- It is not a rank tracker and not the ongoing work.
- Each item should be doable without a second translation.
What an Audit Looks At
Three layers, in an order that keeps the list short. What a crawler can reach and what is indexed. What the templates do to every URL they generate. What the commercially important pages actually say. Technical SEO is the first two when the finding is a crawl or a template. On-Page SEO is the third when the fetch is clean and the words are wrong.
A five-page brochure and a catalog of thousands of URLs are different audits. Agree which one you are buying. A crawl of the homepage alone is not an audit of a catalog. A crawl of every URL with no one deciding which pages matter is not a list. It is an export.
Search Engine Optimization is the wider practice. The audit is the look that tells you where to start inside it.
The useful list is short enough to pick up.
What You Should Receive
You should be able to do the next thing, or hire it, without asking what the sentence meant. A useful item names the URL or the template, says what is wrong, and says what to change. The items are ordered by what blocks the next improvement, not by how dramatic they sound.
You should also receive the things that are fine, briefly, so you do not pay to redo them. An audit that finds a problem in every row has not looked. It has filled a template.
Ask for the list in a form you can keep. A slide that cannot be copied, or a login you will lose, is a weak delivery. The point of the document is that you still have it when the call is over.
What an Audit Is Not
It is not a rank tracker screenshot. It is not a plugin score. It is not a promise that traffic will arrive by a date. It is not the months of work that follow. Those months are a different engagement, described in the comparison of an audit and ongoing SEO.
It is also not a rewrite of the site disguised as a finding. "Replace the website" can be a real conclusion when the template cannot be changed and hides the content. It is not the first line of every audit. Most lists start with a rule, a canonical, a title, or a page that should not exist.
If the only artifact is a score that moved, you did not receive an audit. You received a number.
What Happens After the List
Someone does the items, in the order written, or you decide not to. The audit's job ends when the list is clear. Implementation is the next contract, the next month, or your own developer. Do not let a vendor blur the line so the audit can never be finished.
A practical handoff:
- Confirm the scope matched the site you have.
- Read the first five items and see if a person could do them.
- Assign an owner to each, even if the owner is "not now."
- Fetch one corrected URL before you commission the rest.
| You asked for | You should hold | You did not buy |
|---|---|---|
| An audit | A short ordered list with URLs | A rank or a date |
| A technical finding | A task a developer can ship | A new site by default |
| A content finding | The query and the page that disagrees | A blog calendar |
| The end of the audit | The list, in your hands | A retainer you cannot pause |
The last row is the one vendors blur. An audit you cannot finish reading is not finished work.
How to Use the List the Week It Arrives
The week the audit arrives is the week it either becomes work or becomes a file. Open the list and sort it into three piles before you forward it to anyone. Pile one is fetch: a URL that redirects badly, a template that hides the text, a preferred address that was never named. Pile two is words: a title that disagrees with the first screen, two URLs that want the same query. Pile three is everything else, including mentions, content ideas, and tool scores. Do pile one first. Do pile two on the URLs that survived pile one. Leave pile three until those are moving.
The list should already be in something like that order. If it is a flat export of every warning a crawler emitted, do the sort yourself and send the unsorted version back with a question: which ten items would you do first, and which URL does each one change? An audit that cannot answer that is a scan. SEO Audits is the scan turned into a sequence. The week the list arrives is when you test whether that sequence is real.
Assign a name to each item you keep. A developer owns a redirect. An editor owns a title. You own the decision when two pages compete. An item with no name will sit in the list until the next audit repeats it. That repetition feels like news. It is the same undone task.
Do not start a retainer in the same week unless the list named the ongoing work. Ongoing work is what you repeat after the fixes: watching Search Console for the URLs you changed, and writing the next query only when the current one is clear. A monthly call that re-reads the audit is not ongoing SEO. An Audit and the Work After It separates those clocks so you do not pay twice for the same PDF.
Write down what you refused. A recommendation to rebuild the site, to buy links, or to add a city you do not serve can sit in the file with a no next to it. Refusal is part of using the list. So is disagreement. If an item describes a page you know is wrong, correct the item before anyone builds it. The audit is a look at the site as it was. You still decide what the site is for.
At the end of the week you should have a shorter list than the one that arrived, with names on it, and a sentence about what will be true when the first three items are done. If you cannot write that sentence, you received a document, not an audit you can use.
Questions
How Is an Audit Different From Technical SEO?
Technical SEO is the layer: crawl, index, templates. An audit looks at that layer and at what the important pages say, and it ends in one ordered list. You can fix a known technical issue without commissioning the full look.
Who Is the Audit For?
For someone who can act, or who can hire the action. A document no one will read is not a reason to buy one. If you already know the three URLs that are broken, fix those before you buy a wider look.
Does a Small Site Need One?
Sometimes. A short look at five pages can still be an audit if it ends in a list. It should not be priced or scoped like a catalog. Agree the size first.
What If I Disagree With an Item?
Say so. The list is about your site, and you know what you sell. An item that recommends a service you do not offer is a bad item. Cross it out. Do not throw out the items you can check.
Conclusion
An SEO audit is a look at the site as it is, ending in a short list you can act on. It covers what is indexed, what the templates do, and what the important pages say. It is not a score, a rank, or the work that follows. When you hold the list, the audit is done.
If you want that list from the site you have now, Speak With Us.
