Nobody can rank the work
You have a folder of issues and no sequence. Engineering will not pick. Content will not pick. Leadership wants a date that nobody should invent. An audit ranks severity and effort so the next 90 days have an order.
SEO audit
SEO Audit for One Website: What Is Broken and What Can Wait
An SEO audit at SEOConsultants.ai is a time-boxed diagnosis of one website. We review crawl, templates, content quality, cannibalization, links, and how clearly the brand is named on the page. You leave with a ranked fix list and a 90-day sequence. We stop at diagnosis. This is not a consulting retainer, not a store catalog review, and not an AI search audit.
- Access
- Baseline
- Findings
- Handoff
Position
We diagnose one website, then we stop
Most teams do not need another 200-page PDF. They need to know what is actually broken, what can wait, and what was never this job. An SEO audit exists for that snapshot. One site. A dated baseline. Findings ranked by severity and effort. A sequence someone can put into tickets. Then the work ends unless you buy a different service.
The store catalog
Product indexation, collection templates, facets, and variants are an ecommerce SEO audit. Glancing at a homepage is not a catalog diagnosis.
Open ecommerce SEO auditThe answer surface
How models describe the brand, and whether you appear in Google AI Overviews, is an AI search audit. Classic crawl findings can support that work. They are not that work.
Open AI search auditThe crawl program
Technical SEO keeps access true after the snapshot: crawl, index, and releases that strip robots or canonicals. An audit names those issues. It does not become the engine.
Open technical SEOThe retained advisor
SEO consulting sits inside decisions after you know the constraint. An audit can send you there. It does not replace the snapshot with a weekly call.
Open SEO consultingThis is a website SEO audit. Marketing sites, SaaS product sites, and publishers belong here. A product catalog belongs on an ecommerce SEO audit. How the brand shows up in generated answers belongs on an AI search audit. Ongoing crawl and index work belongs on technical SEO. Advisory after the snapshot belongs on SEO consulting.
We will not inflate severity to sell a retainer. We will not invent a ranking date. We will not fold a store diagnostic and an answer-surface review into one generic health check so the proposal looks complete. If we cannot fetch the site as a crawler would, we will send you to the service that actually owns that work.
When to buy
When you need a diagnosis, not a retainer
Buy an SEO audit when the website is still the unknown. If you already needed a catalog review, an answer-surface review, or a retained advisor, start on those pages instead.
The last PDF was a scare
Someone sold a health score, a traffic apocalypse, or a ranking guarantee. You need evidence you can check: crawl samples, Search Console, and templates that fail the query they claim to answer. If we cannot show the page, we will not write the finding.
The audit keeps turning into a retainer
A vendor delivered a dump, then stayed to implement everything under the same heading. Diagnosis and delivery are different jobs. This work stops at the handoff. Shipping lives on the matching service.
The risk might not be this website
If the risk is the catalog, buy an ecommerce SEO audit. If the risk is generated answers, buy an AI search audit. If you already know the constraint and need owners, buy consulting. Stay here when one website still needs an honest baseline.
Process
How we work
Four steps: Access, Baseline, Findings, and Handoff. Each step has a named outcome. We do not start a technical retainer inside step four. The process exists to make one snapshot true.
-
Access
We collect what the crawler and Search Console can already see: property access, analytics, robots, sitemaps, and a way to fetch HTML. If a log or export is missing, that is a finding, not a reason to invent a score. Store-only admin belongs on an ecommerce SEO audit when the catalog is the real job.
Outcome A named evidence set, including what we do not have.
-
Baseline
We crawl and sample templates. We mark indexable surfaces, title and canonical conflicts, pages that miss search intent, cannibalization, link risk, and entity names the document never says. We are looking at the HTML a crawler gets, not a plugin screenshot.
Outcome A dated picture of one website.
-
Findings
We rank issues by severity and effort. Quick template fixes sit above multi-month rebuilds. We write ticket-ready detail: the URL pattern, the evidence, and what done looks like. We do not dump 200 unranked rows. The workshop exists to agree the sequence, not to add a second report.
Outcome A sequenced list leadership can refuse or fund.
-
Handoff
We stop. The 90-day sequence names who should own each cluster of work: technical SEO, on-page, content, consulting, or a different diagnostic. If you want us to ship, that is a new engagement. An audit that quietly becomes a retainer has failed this step.
Outcome A closed snapshot, not an open-ended weekly.
Outcomes
Expected outcomes
An SEO audit produces a snapshot you can act on or refuse. It does not produce a ranking overnight, and it does not replace a catalog review or an answer-surface review.
Leadership summary
What is broken, what can wait, and what belongs somewhere else. Short on purpose. A novel is not a summary. Named traffic figures appear only when Search Console can support them.
Ticket-ready findings
URL patterns, evidence, severity, effort, and what done looks like. Engineering can file from this. Content can file from this. A screenshot with a red circle is not a ticket.
90-day sequence
Order of work, not a calendar of ranking dates. The sequence can be refused. A refused sequence is still an audit outcome. We will not invent a date Google does not owe you.
Severity and effort map
What is blocking indexation versus what is a content gap. The map is dated. Last year's crawl is not this map.
Handoff note
Which service should own shipping, and which diagnostic should own leftover work we will not fake here. Catalog leftovers go to an ecommerce SEO audit. Answer-surface leftovers go to an AI search audit.
Benefits
Key benefits
A sequence instead of a dump
The team knows what to do this month. Unranked findings are how 200-page PDFs sit unread.
Evidence you can check
Each finding points at a page, a crawl sample, or a Search Console row. If we cannot show it, we will not write it.
A stop that holds
Diagnosis ends. Shipping starts on the matching service, or it does not start. The audit is not a quiet path into a retainer.
The right door after the snapshot
Store issues, answer-surface issues, crawl programs, and advisory each have a page. You are not asked to buy all four because the proposal needed length.
Operating model
The snapshot we actually ship
An SEO audit only works when evidence is visible. If nobody can fetch the HTML, we are scoring a plugin, not diagnosing a site.
Every SEO audit starts from four facts: the commercial URL family that must serve a real query, the system that renders it, the person who can grant crawler-visible access, and the service that should own shipping once findings exist. If any of those four is missing, we spend the first days naming it. We do not fill the week with a tour of SEO specialties.
We test the document, not the editor. Does this page match search intent in the HTML? Does coverage have topical relevance, or is it a pile of similar drafts? Keyword density is not an audit metric. If a page is a client-rendered empty shell, the finding is render. A non-template build or technical SEO may own the next step. The audit still names it.
The roles below are the default for a snapshot. You may change them. You may not leave access implied. Implied access is how we get a CMS preview and call it a crawl.
- SEO audit lead SEOConsultants.ai collects evidence, ranks findings, and writes the handoff. We do not silently become your technical SEO vendor because the list was long.
- Engineering Grants fetch access and confirms what a release can change. A blocked log is a finding. It is not a reason to guess at JavaScript rendering.
- In-house SEO Names the commercial URL family and whether a finding is already in flight. They are not asked to defend last year's health score.
- Content Confirms which templates are supposed to answer which queries. They may refuse a type that would only add cannibalization.
- Leadership Funds or refuses the 90-day sequence. An unread summary is not an audit failure. An invented ranking date would be.
On the evidence
What we inspect first
The first session is for access and the pages that must earn the next useful visit. It is not a tour of packages you could install.
We ask for the site that is actually in question. A marketing domain, a docs subdomain, or a product site are all valid. 'Audit everything we own' is not, until the properties are listed. If the work is a catalog, we stop and send you to an ecommerce SEO audit. If the work is how ChatGPT describes the brand, we stop and send you to an AI search audit.
We then fetch what the crawler fetches. View source, rendered HTML, robots, sitemaps, and Search Console coverage. We compare that to what the editor believes was published. The gap is often the job. A preview that looks complete while logged into the CMS is not evidence.
The last part of the session is the baseline window or the stop. A baseline names the property, the freeze, and the first artifact we owe. A stop names the access that is missing. Both are audit outcomes. A shopping list of five SEO apps is not.
AI search and LLMs
How AI search questions get handled in an audit
An SEO audit can say whether a page is eligible for classic results. It cannot become the AI search audit or a citation product.
Leadership now asks whether a page will appear in Google AI Overviews (AIO) or in a chatbot answer. Those questions are real. They are not all this work. If the crawler still cannot fetch a body that matches the query, the issue is eligibility on a page you own. If the HTML is honest and the brand is misdescribed in generated answers, that is an AI search audit. If you need a retained program across search UIs, that is AI SEO.
Eligibility first
If the body is missing, blocked, or off-intent, no amount of entity language in a CMS field will help generative search. The audit names that. It does not sell Overview presence.
Entity names on the page
We check whether the organization, product, or place is named in words a human would use. That is entity optimization as a test of the document, not a Knowledge Graph program we sell from this audit.
Route the rest
Answer-surface measurement belongs on an AI search audit. How models describe the brand at length belongs on LLM SEO. An SEO audit will not treat a citation as a score we can ship from a crawl.
Schema
Structured data as a finding, not a launch
JSON-LD can help extractors read a page that already tells the truth. In an audit, invalid markup is usually a second copy of a lie the HTML already told.
HTML first
We report Organization, Product, or Article markup that disagrees with the document. We do not add a graph from this engagement. Implementation belongs after the snapshot, on technical SEO or the matching build.
Owner of the script
The findings name which system emits JSON-LD when two apps inject two graphs for one path. That is a ticket. It is not a reason to stay as a schema retainer.
No citation shortcut
Extra fields will not force generative search to cite you. An SEO audit can stop a schema project that is being used instead of fixing the template. Eligibility is not a purchased mention.
Teams
Working with engineering, in-house SEO, and agencies
An SEO audit assumes someone can grant evidence. We plug into that path. We do not replace it with another dashboard login.
Engineering
Usually the people who can confirm rendering, robots, and the next release. Our job is a finding they can file. We do not open fifty tickets that belong on technical SEO after the snapshot exists.
In-house SEO
Chooses the commercial URL family and defends the sequence when a campaign wants every finding done this week. They are not asked to become crawler operators. They are asked to stop accepting health scores as proof.
An agency already on the site
Can keep writing or shipping once the sequence is honest. If the agency is trying to run the audit as more blog posts on a thin template, two jobs collide. We will say that in the findings. Catalog specialists belong on an ecommerce SEO audit when that is actually the work.
Questions
Frequently asked questions
When should I buy an SEO audit instead of SEO consulting?
Buy an SEO audit when the website is still the unknown. You need a dated diagnosis: what is broken, what can wait, and what is already fine. Buy SEO consulting when the bottleneck is already named and the gap is judgment: who may refuse work, who owns the backlog, and how often leadership reviews organic search. An audit can send you to consulting after the snapshot. Consulting does not replace the snapshot with a longer meeting.
When should I buy an ecommerce SEO audit instead?
Buy an ecommerce SEO audit when the risk lives in the catalog: product indexation, collection and product templates, facets, variants, and merchandising gaps. This is a website SEO audit. A marketing site, a SaaS product site, or a publisher can stay here. A store whose problems sit in the catalog should not. We will not run a cart diagnostic under a generic audit heading.
When should I buy an AI search audit instead?
Buy an AI search audit when the question is how the brand appears in generated answers, Google AI Overviews (AIO), or other answer surfaces. This page diagnoses classic eligibility on pages you own: crawl, templates, content that matches search intent, and cannibalization. Those findings can support AI search later. They are not a citation review. If the HTML is already honest and models still misdescribe you, open the AI search audit.
Does an SEO audit replace technical SEO?
No. An SEO audit is a snapshot. Technical SEO is the ongoing work of crawl, index, and access after that snapshot. We will name crawl and index issues here, with severity and effort. We will not stay on as a technical retainer because the report was long. If the finding is access that has to stay true every release, that work belongs on technical SEO.
What access do you need, and what will you not invent?
We need Search Console, analytics, and a way to fetch what the crawler fetches. CMS or repo access helps when templates are the issue. We will not invent ranking dates, traffic lifts, or a competitor score we did not measure. If a log, a crawl, or a Search Console export is missing, that gap stays a gap. We write it down. We do not fill it with a scare number.
One website snapshot
Need a ranked fix list for one live website?
Send the domain and what you already know is broken. We will say whether a website SEO audit is the right product, or whether a catalog or answer-surface diagnostic should go first.
- One website
- Then a stop
- Findings with evidence
- No open retainer from the PDF
Access, baseline, findings, handoff. Then a stop.