Role
SEO
How long does it take before a change you make shows in anything visible? Months - and the reckoning comes every month. That tension is built into this role and no tool removes it; what can be removed is the work that fills the time between one change and the next.
Intro call
Four questions we would start with
How long before you notice that traffic to an important page has fallen?
With a monthly report - up to thirty days. In that time the page loses position, and the cause, usually trivial and technical, has time to settle in.
How do you know which pages actually bring clients rather than just traffic?
If you do not know, you are optimising for the number of visits. That is the metric that grows most easily and means least.
Which technical problem comes back most often?
Usually the same one: duplicate URLs, missing descriptions, redirects after a release. It comes back because an audit is an event every six months and releases happen every week.
What do you not do, even though you know you should?
Internal linking, updating old texts, category descriptions. Important tasks, never urgent - they lose to every request for new content.
We take over the monitoring and the inventory, you keep the strategy
Keyword research, detecting regressions, the technical audit and the content inventory can be taken off the desk. What follows from it and where to invest time is settled by a person.
- We do not produce content for keywords. - That is the road to a site full of texts nobody reads, and to a penalty rather than to visibility. We take over the analysis, not writing at scale.
- A regression comes back as an event, not as a row in a report. - A drop on an important page should reach you in the week it happens, together with what changed then.
- The technical audit is continuous, not periodic. - A problem created at a release surfaces straight away rather than at the next review in six months.
Scope
What can be taken off SEO work
Twenty example tasks. Each one has a human approval point. Below is a selection, and the scope we fit to your process.
Keywords and intent
- Keywords the site is now visible for and was not before
- Grouping queries by the intent behind them (judgement of intent: the specialist)
- Pointing out queries with no page answering them
- Comparing visibility with competitors on a chosen set of keywords
- Catching queries that appear seasonally
The technical audit
- Continuous monitoring of indexing errors and page statuses
- Detecting duplicate content and URLs
- Checking redirects after every release
- Pointing out pages that load slowly on mobile
- A summary of gaps in descriptions, headings and structured data
Content for a query
- Analysis of what an existing page lacks against a query (decision to change: the specialist)
- A list of pages older than a year with falling traffic
- A proposed scope of update for a particular page
- Detecting cannibalisation - several pages competing for the same query
- A starting draft of a category description (edited by: the specialist)
Linking and measurement
- Proposed internal links between existing pages
- Detecting pages with no link pointing to them
- Monitoring lost external links
- A report split into pages bringing traffic and pages bringing enquiries
- What changed on the site in the period in which the traffic changed
A day's work
Today
- You learn about a drop at the monthly report
- You run a technical audit every six months and find the same things every time
- At every release you check the redirects by hand, or not at all
- You do not know which of several hundred pages is worth refreshing first
- You have been putting internal linking off for quarters
- You assemble the report from three tools, each counting differently
With AI assistance
- A drop on an important page reports itself in the week it happens
- Technical errors surface at the release, not at the audit
- The list of pages to refresh is ordered by potential rather than by age
- The linking proposals are waiting; you decide which make sense
- The report assembles itself, and you write the conclusions
- You have time for what the tool will not do - deciding what is worth the effort
- Query coverage
fewer queries with no page answering them
the gaps are visible as a list rather than discovered by chance
- Detecting a regression
a drop comes from monitoring rather than from the monthly report
positions are checked continuously, not at the close of a period
- Technical debt
the same error does not come back after every release
the check happens at the change rather than at the review
- A repeatable audit
the audit stops being a project
it becomes a state you can see every day
We start with monitoring, not with producing content.
- Step 1
We pick the pages that actually matter
Usually a dozen or so URLs account for most of the valuable traffic. They get monitoring first - the rest can wait.
- Step 2
Monitoring and a continuous audit
Regressions and technical errors come back as events. This is the stage with the fastest effect and it asks nothing of the rest of the organisation.
- Step 3
The content inventory
What you have, what duplicates, what is missing against the queries. Only with that map does a conversation about new content stop being guesswork.
- Step 4
Linking and updates
Continuous work that has never been urgent. Now it has a list and an order.
Common questions
Questions that come up at the first meeting
Will an SEO specialist still be needed?
They will, and more than today. Today's work is largely gathering data and assembling reports - and the decisions about content, site structure and which topics are worth taking on at all are made by a person anyway. When reporting stops taking a week a month, there is time for the second part, the one that actually changes results.
Does this fall under the AI Act?
Analysing visibility is not a high-risk use. More relevant here are the search engines' own rules on content - and those we treat as a line we do not test.
Still have a question that is not here? Book a call
Next step
When did you last learn about a drop in traffic in the same week it happened?
We will show you what work on visibility looks like when monitoring and auditing stop being an event every six months.