The short version
An employer asks an assistant for a specialist agency. The reply may name three firms, cite two websites, mention yours in passing, or mention none of you. Those are different facts, and folding them into one cheerful percentage is how a report becomes impressive while remaining commercially empty.
You cannot purchase a guaranteed appearance. You can make the public explanation easier to find, easier to read and easier to check, then write down what actually happened. The chance improves when the desk’s real judgement is sitting in ordinary HTML, the readers you want are allowed to fetch it, and the organisation on the page matches the organisation in the markup, after which the assistant still does whatever it wants with the result.
Seven observations, counted separately
Vendors have been busy renaming search, AEO, GEO, answer engines, generative engines, while Google’s current guidance is blunter: its AI features are still search, grounded in the ordinary index, and the useful work is still useful pages plus ordinary technical hygiene. If a supplier is selling a secret AI schema, a mandatory llms.txt file, a fixed answer length, or a score that pretends schema depth causes recommendations, they are selling a theory Google has already asked you to ignore.
That does not make every assistant identical. OpenAI separates the bot that may show you in ChatGPT Search from the bot that may use a page in model training, and from the user-triggered fetch that happens when someone asks a question. Training permission does not get you into Search, and blocking “all AI” because a blog said so can remove the one reader you still wanted.
Google finds further pages through ordinary HTML anchors with real href values. A library that exists only as a data file, or a method that can be reached only by a scripted click, is not a discovery path. JSON-LD is how we write the visible ScopeSite and RWD facts down, and a format is all it is.
- Crawlability: a wanted crawler can request the page and follow its ordinary links.
- Indexing: the URL is in that product’s index, or a report says it is not.
- Retrieval: a dated prompt caused a live fetch or grounding event, rather than a stored answer.
- Brand mention: the agency or identifiable desk appears in the answer text.
- Source citation: one of its URLs is shown as a supporting link.
- Visits: a session reached the public page under the configured analytics rules.
- Qualified enquiry: a suitable employer started a conversation the agency can actually trace.
A current starting count, with the limits still attached
On 25 September 2026 we pulled Recruitment Web Design’s own Search Console web-search data for 26 August to 22 September: nine page rows, eighty-two page-level impressions and two clicks. The website-company comparison article accounted for 18 impressions and one of those clicks, pricing had eight impressions and the other click, and the website-design, ATS and software pages had impressions and no clicks.
That is a starting count for this site, too small for a before-and-after study, a ranking or a speech about momentum. The useful part is the discipline: a date range, a property, a page list, and a refusal to pad the story.
The same window does not tell you what an assistant said. A mention or citation check needs its own log: write the buyer question first, then the engine, the mode, the date and the geography, and score the seven fields independently. If you skip the prompt and the date, you do not have a measurement. You have a memory of being pleased.
No assistant transcript is invented here, because inventing one would be a rather neat way of demonstrating the problem.
The approved named proof of the wider method sits on the published H4TLT case study, which is about workplace hearing surveillance. Read that page for the evidence the client has permitted, which is not a recruitment placement result and does not travel into this site’s two clicks.
The work you can actually commission
Start with the conversation the director already has when the work is going well: which roles, which employers, and what “good” looks like once you drop the slogan. If that explanation lives only in someone’s head, or in a PDF last saved under a consultant who has since left, the website is asking a stranger to finish the brief.
Write the missing facts on the relevant page, in the first HTML response. Google can run JavaScript, while other readers may never execute a script, so putting the important words in the first response is a design choice with a reason rather than a claim that every bot is helpless or that inclusion has been decided.
Then check who is allowed in. Search access and training access are separate decisions. A firewall that challenges every unknown user-agent can also challenge the one you meant to welcome. OpenAI’s own notes say a robots change can take around a day to settle. Patience is part of the method, which is irritating, and still true.
Keep the names consistent: ScopeSite is the legal provider, Recruitment Web Design is the specialist brand it supplies, and Dan Cartwright is the author people can actually look up. Structured data should repeat those visible facts, on the same page, without inventing an office, a rating or a second company. Google does not require special AI markup for its generative features. Accurate markup can still help ordinary rich results. Node-count is not a strategy, and there is no AI-readiness score in this method.
- One employer question per page, answered near the top.
- Approved evidence, with a sentence about what it does not prove.
- A next step an employer can use without uploading a CV.
- Crawler rules checked against the bots you intended, rather than a generic “block AI” preset.
- A written prompt set for later comparison, instead of a new article for every wording of the same question.
What the agency supplies, and what sits outside the build
ScopeSite can structure, deliver and test the public explanation. The desk still has to supply the judgement. If the specialism is unresolved, the website cannot make it true, and publishing a planned service as an established one is how you earn a very confident wrong answer later.
Vacancies, if they form part of the public story, follow the system that already owns them. A feed that is a day behind will give search and assistants a day-behind story. That is an operations problem with a website symptom.
- The agency supplies: specialism, geography, approved proof, real employer questions, access, and a person who can sign off wording.
- RWD work, delivered by ScopeSite, controls: page structure, server-delivered HTML, ordinary crawlable links, matching structured data, crawler-policy checks, and the seven-column log.
- Platforms control: crawling, indexing, retrieval, citations and whatever they decide to say on Tuesday.
How the work is done
Discovery starts as a page review. We take one live URL, one employer type and the questions that person would actually ask, then record what the first screen explains, what evidence is visible, where the enquiry goes, and what a first-response reader receives before scripts run.
The change is then small enough to describe: rewrite the unclear specialism, move the answer up the page, fix a blocked crawler, align the organisation name, and stop a closed vacancy from volunteering for work. We do not commission a hundred near-identical location pages because a keyword tool looked hungry.
Observation uses comparable windows, so crawl and index state stay in Search Console, visits stay in the configured analytics, and Google’s generative AI report, where the property has it, records AI Overview and AI Mode link impressions. Bing’s AI report records sampled citations on the surfaces it supports. The manual answer log covers mention, citation and retrieval for the assistants those dashboards do not speak for. Qualified enquiries stay in the enquiry record, and an empty column stays empty rather than being filled to look complete.
What this cannot promise
This work cannot make an assistant recommend you, stop a competitor with a clearer page from being named first, turn 82 impressions into a market, treat H4TLT’s permitted case study as a recruitment testimonial, or use another supplier’s article as a draft.
Other recruitment firms already publish GEO and AEO guidance. That is useful, because it saves us from a silly uniqueness claim. The difference worth offering is a method you can inspect: retained ATS where the connector allows it, labelled demonstrations, dated sources, and counts that refuse to merge.
Give it something true to read, then count what happened.
Recruitment Web Design’s own Search Console window, 26 August to 22 September 2026
Authenticated web-search data retrieved on 25 September 2026: nine page rows, 82 page-level impressions and two clicks. Used as a dated starting count for this site, with no claim that the library improved anything.
- The website-company comparison article recorded 18 impressions and one click, pricing recorded eight impressions and one click, and the website-design service, ATS integrations and recruitment software pages recorded 12, 12 and 11 impressions with no clicks.
- The sample is too small for a trend, a ranking claim or a commercial conclusion. That limit is part of the example.
- The same retrieval is web search, and it does not say what ChatGPT, Claude, Perplexity or Grok answered on those dates.
- A separate answer log would use a written buyer prompt, the engine, the mode, the date and the seven independent fields, with no invented assistant answer attached.
- The approved named method evidence remains the published H4TLT case study in occupational hearing surveillance. Read that page for the client’s own evidence, which is not a recruitment placement result.
What we count, separately
- Crawlability: A wanted crawler can request the page and follow ordinary HTML anchors with real href values, unless robots, firewall or authentication choices block it. Training-crawler permission is a separate decision.
- Indexing: The property’s search index contains the URL, or a Search Console report says it does not. Indexing is not guaranteed after a crawl, a sitemap row or an IndexNow receipt.
- Retrieval: A dated prompt caused a live fetch or grounding event, rather than a stored training-data answer. OpenAI separates SearchBot, GPTBot and user-triggered fetches. Some prompts never retrieve the web.
- Brand mention: The agency name, Recruitment Web Design brand or identifiable desk appears in the answer text for a written prompt, on a recorded date, engine and mode. A mention can be accurate or wrong.
- Source citation: A URL from the agency, or another agreed source page, is shown as a supporting link. Google’s generative AI report, where available, records link impressions. Bing’s AI report records sampled citations on the surfaces it supports.
- Visits: A session reached a public page under the configured analytics rules, recorded in its own visit column beside mention, citation and enquiry rather than standing in for them.
- Qualified enquiry: A suitable employer started a conversation that the agency can tie to a discovery path with its own records. Planner use and demo clicks stay in their own columns.
What Recruitment Web Design controls
- The public wording, page structure and first HTML response we are commissioned to deliver.
- Ordinary crawlable anchors between the pages we publish.
- robots and firewall recommendations for search crawlers, kept separate from training-crawler decisions.
- Consistent ScopeSite organisation, RWD brand and author names that match the visible page.
- Structured data that restates those visible facts, with no extra invented company, office or rating.
- The written prompt set, observation dates and the seven-column log.
What the agency supplies
- The specialism, geography and employer type the agency wants to be found for.
- Approved evidence and the sentence that limits what it proves.
- Website, CMS, DNS and approval access.
- Whether live vacancies form part of the public story, and which system owns them.
- The employer questions already asked on calls.
What this cannot guarantee
- Crawling, indexing, retrieval, appearance, citation or recommendation.
- That a prompt will trigger a live web fetch.
- That schema depth, llms.txt or a readiness score will cause an assistant to name the agency.
- That visits become qualified enquiries.
- A first-or-only position among recruitment suppliers.
Sources
- Optimizing your website for generative AI features on Google Search
Google Search Central. Checked . Primary technical source. Current Google rules for useful original pages, ordinary SEO, and the absence of special AI schema or llms.txt requirements. Google Search guidance only. It does not describe ChatGPT, Claude, Perplexity or Bing, and it does not guarantee indexing or appearance.
- Understand JavaScript SEO basics
Google Search Central. Checked . Primary technical source. Confirms that Google can render JavaScript, so JS-blind claims cannot be applied to Google Search. Does not describe every AI crawler, and rendering is not a ranking or citation promise.
- Structured data general guidelines
Google Search Central. Checked . Primary technical source. Markup must match visible content. Valid JSON-LD does not guarantee a rich result. Policy for Google rich results, not a mechanism that causes AI recommendations.
- Link best practices for Google
Google Search Central. Checked . Primary technical source. Library and service links must be ordinary anchors with real href destinations and descriptive text. A method page reachable only by script is not a discovery path. Google Search crawl discovery only. It does not describe assistant retrieval or guarantee indexing.
- Generative AI performance report
Google Search Console Help. Checked . Primary technical source. Defines AI Overview and AI Mode link impressions as a Search Console observation. Impressions are not recommendations, citations in other assistants, or enquiries.
- Overview of OpenAI crawlers
OpenAI. Checked . Primary technical source. Separates OAI-SearchBot, GPTBot and ChatGPT-User. Training permission is not required for ChatGPT Search. OpenAI product controls only. robots.txt updates can take around 24 hours to apply.
- JSON-LD 1.1
W3C. Checked . Primary technical source. Named graphs and identifiers for connecting real entities. A format choice, not inclusion in any vendor knowledge graph.
- AI Performance in Bing Webmaster Tools
Microsoft Bing. Checked . Primary technical source. Defines sampled citation and grounding activity on supported Microsoft surfaces. Observational and sampled. Not an all-AI share, competitor ranking or enquiry count.
- Spam policies for Google web search
Google Search Central. Checked . Primary technical source. Blocks scaled unoriginal pages and copied competitor articles as a delivery method. A policy boundary, not a traffic forecast.
- H4TLT published case study
ScopeSite. Checked . Approved claim. The only currently named client proof. Method evidence in occupational hearing surveillance, not a recruitment result. Do not restate unverified traffic or revenue, or treat a cross-sector case as a recruitment outcome.
- Recruitment Web Design Search Console web-search pages, 26 August to 22 September 2026
Google Search Console, retrieved for the RWD library plan. Checked . First-party measurement. Dated first-party starting count: nine page rows, 82 impressions and two clicks. Used as a measurement example, not a campaign result. A short, low-volume window. It cannot support trend, ranking or commercial conclusions, and it is web search rather than every assistant.