AI search, SEO & online discovery
Practical coverage from Dubai

Saved
Technical SEO

How to Test an AI-Friendly Website Without Creating a Separate AI Site

Summarize with AI
Planning and reviewing a website interface; illustrative photograph.
Photo by picjumbo.com / PexelsIllustrative photography
In this article 5 sections

A business is told to build a second version of its site for AI. Its existing service pages already explain the offer and give customers a way to enquire. Before funding a second publishing system, the owner can ask a smaller question. Can a new visitor open the actual service page, read the decisive facts and find the next step? Can the relevant platform access that same public address under its documented rules?

Use the live customer website as the test surface. Choose a few important pages and record what an ordinary request, a clean browser and an authorised platform check can each establish. The existing AI Visibility access checklist covers basic crawl access. This walkthrough ties those checks to a real customer journey and helps decide whether the work belongs in the current page, a shared template or a legitimate new page. AI Visibility site access checklist

Choose a customer question and the page that should answer it

Write down a question a real customer might ask. For a service provider it could be “Do you offer this service in Dubai, and how do I ask for a quote?” Identify the page the business wants a person to use. Choose a few decisive facts, such as the service name, locations covered, a condition on the offer and the route to enquire. Ask the content owner to confirm what should be public and current. If the business has separate location or language pages, identify the intended version for each audience.

Test the page someone would land on directly. A visitor arriving from a search result can miss the explanation on the homepage. Give the destination enough context to identify the business and the service before it asks the visitor to act. Choose a stable content marker for the test. A broad phrase in the navigation or footer may appear even if the service content itself is missing.

Question Evidence to collect Where a fix may belong
Does the public address deliver the right page? Status, final URL and content marker Routing or hosting
Can the intended reader find the facts? Initial HTML and clean browser observations Template, content or rendering
Can the reader take the next step? Visible, labelled contact or booking route Page layout or action owner
Can the platform access it? Platform guidance and permitted test evidence Crawler policy or delivery
Is an AI answer citing or recommending it? Separate recorded answer or supported platform metric Measurement workflow

Build a small test set before checking anything. Choose one service page where a customer decides whether the offer fits, one contact or booking destination and one supporting page that answers a common follow-up. Give each a primary question and a source for the expected answer. An editor can check whether the page says what the business intended, while a technical owner checks whether the relevant text and route are available. The split helps avoid a situation where a vague offer is treated as a rendering problem or a missing request is treated as a writing problem.

Test the same address in the response and the browser

Request the exact public URL and save the status, final address, type and original HTML. Search for the marker in context. If it appears in a data object but not the main body, make that distinction in the record. A successful code can still return a generic page or a shell. Open the same address in a clean browser and check that the content appears in the intended place. If a service detail depends on a script, record the request or interaction that supplies it. Google technical requirements · Google JavaScript SEO basics

A small first pass can use the following command and then a browser check. Replace the address with a public page you are authorised to test. Save a copy of the evidence and the observation date so you can compare the same route after a change.

url='https://example.com/replace-with-the-customer-page'
curl --silent --show-error --location --max-redirs 8 --max-time 20 \
  --dump-header page.headers --output page.html \
  --write-out 'status=%{http_code} final=%{url_effective}\n' "$url"

Use a narrow viewport as well as the layout the team normally sees. Check the service heading, the location or scope statement and the first meaningful action. If a button opens an enquiry panel, confirm the label and destination. Stop before sending a real enquiry unless a test submission is authorised and routed safely. A visible submit control and a successful delivery test establish different things.

A JavaScript-disabled pass can show which facts the original page supplies without the scripts. It is a useful diagnostic for the customer page. It does not emulate every search crawler. Google documents its own rendering process, and OpenAI identifies distinct crawler and fetcher purposes. Interpret any platform-specific conclusion using the evidence for the platform you mean. Google JavaScript SEO basics · OpenAI crawler documentation

Work through a real service page

On 6 November 2026, the public Lunasol GEO service page returned HTTP 200 and an HTML content type. The original response contained a service heading identifying GEO and Dubai, and the page declared its own address as canonical. A clean Chrome check at 390 pixels wide found the heading visible and the labelled enquiry button present and visible. The test repeated with JavaScript disabled and observed the same heading, canonical and enquiry control. No form was submitted. Lunasol publishes AI Visibility, so this is a related-party example of the method. Lunasol GEO service page · About AI Visibility

That result supports a limited statement. A public visitor could load the tested service page and locate the visible heading and enquiry control under the sampled conditions. It does not establish whether the enquiry would be delivered, whether all details work with scripts disabled, or whether a platform has indexed the page. The next evidence to collect depends on which question the business still needs answered.

Repeat the same steps on a few pages with different responsibilities. A branch page might use another template. A product page may load prices separately. A guide may have a usable public explanation but lead to a different contact route. Keep a representative example of each problem and identify the owner. If several pages lack the same visible information, review the shared template before building new copies of individual pages.

A website launch can also be publicised through social media. Shopify’s launch guide embeds an official post from A.EMERY as part of its coverage of announcement approaches. A social post and a public service or shop page serve different points in the journey. Keep the durable facts and next step available at the destination the reader will actually open. Shopify launch guide with the official A.EMERY post

Consider a business with a public service overview and a booking tool on another host. Test the service facts on the overview, then verify that its link opens the intended booking screen and that the screen identifies the right service. If the booking tool needs scripts to show available dates, record the dependency and the error state separately. The answer to a general question about where the service operates can still live on the overview, while dates and customer-specific options remain in the tool. The audit can preserve a normal booking journey while making the stable facts easier to verify.

Apply platform guidance to the existing page

Google’s documentation for AI Overviews and AI Mode says no additional technical requirements or special AI markup are needed for those Google Search features. It advises the same Search foundations, including making important content available in textual form and making it discoverable through links. The documentation also distinguishes technical eligibility from whether a page is shown. Apply this to the existing public page first. Other products may have different controls, so keep the platform name with any conclusion. Google Search AI features guidance

For a platform that publishes crawler guidance, check the role and applicable directives for the exact address. A policy decision about training can differ from a decision about automated search. If you have permission to inspect logs, look for the relevant verified requester and the response it received. If you have access to a webmaster tool, record which view you checked and when. The worked service page test used public requests and browser rendering, with no private logs, platform inspection or live assistant test. OpenAI crawler documentation · Google Search Console URL Inspection

Consider the maintenance cost before adding a parallel copy. A second page can develop a different price, contact route or description after the next update. If the existing service page lacks a clear answer, add the missing fact in the relevant section or fix the delivery dependency. A separate page can make sense when it serves a distinct language, audience or task with its own owner. Give that page a normal internal route and make its purpose clear to the reader.

Keep the audit tied to the page customers use

Use a Customer site test record with the customer question, exact page, owner, expected facts, ordinary response, clean browser result, action check and any platform evidence. Identify the smallest change that would make the customer’s next step clearer. For a service page with a visible headline but a buried location condition, move or summarise the condition where the reader makes the decision. For a broken booking link, fix the link and verify the intended destination.

If the audit finds disagreement between a help page and the main offer, have the business decide which wording is current. Fix the source that maintains the fact and update other public references that still matter to the reader. A separate copy would introduce another place to reconcile. If the issue is that two audiences need different answers, write down the distinction and test each destination against its own customer question.

Make the acceptance check concrete. For example, a visitor arriving directly on the Dubai page can identify the service and reach the labelled enquiry control from a clean mobile session. Include which facts were checked and where the tester stopped. A later tester can reproduce the same result without guessing whether the exercise included submitting details or waiting for a reply.

After the change, retest the same page under comparable conditions. Keep the control and the original record so the team can tell which behaviour changed. If you want to assess citations or recommendations separately, define the platform, question and observation window. A repaired customer route is an outcome the business can confirm immediately. A change in what a platform says requires its own evidence.

AI Visibility is published by Lunasol, which offers GEO and AEO services. The worked example uses public HTTP and browser observations on Lunasol’s site. About AI Visibility

You’ve reached the end of this article. Read as plain text

Search the blog

Summarize with AI

Choose your assistant. Copy the article and summary request, then paste it into a new chat.

The full article is included, so your assistant can read it without opening this website. Nothing is submitted automatically.

View or copy the summary requestOpen assistant

Summaries are generated by your chosen service and may miss details. Its account requirements and terms apply.