How do I map every subdomain and its intended job?
Start by listing every live subdomain and assigning each one a clear purpose, audience, and relationship to the main domain. Include product, help, developer, status, regional, campaign, and legacy hosts, even when they appear outside the main navigation.
Record the canonical hostname, URL patterns, language, primary audience, and owner for each subdomain. Then mark whether the host is meant to rank independently, support the main brand, or remain out of search. A subdomain that serves customers and a subdomain that serves developers may need different prompts and different success criteria.
Check for forgotten hosts, duplicate environments, old campaign pages, and documentation that still describes retired products. Check whether each host uses a consistent brand name and links clearly to the main site. Do not assume that a subdomain is invisible simply because it has little organic traffic. AI answers can cite a useful support or developer page without citing the corporate homepage.
The output of this step should be a host inventory, not a list of pages. It becomes the reference for deciding whether an answer mentions the right subdomain, the main brand, or neither.
Choose prompts that expose subdomain attribution
Build prompt groups that test whether each subdomain is associated with the right customer question. Use category, comparison, use-case, implementation, troubleshooting, and branded prompts, then include follow-up prompts that ask for a specific resource or next step.
Check whether an engine names the company but cites the wrong host. Also check whether it cites a subdomain without identifying the parent brand, recommends a competitor, or answers correctly but points to a page for a different audience. These outcomes are different problems and should not share one visibility score.
Keep the wording stable while you compare engines and dates. Track the question, engine, answer, cited URLs, cited host, brand mention, competitor mentions, and the subdomain that should have supplied the answer. Run the same prompt set across ChatGPT, Perplexity, Gemini, Claude, Grok, Google AI Overviews, and Google AI Mode.
Cituna tracks mentions and citations across all seven of those engines every day, showing which competitors and pages they cite instead. Its prompt coverage can help establish a baseline, but the key decision remains which host should answer each buyer question.
Separate brand visibility from host visibility
Measure two outcomes separately: whether the brand appears in an answer, and whether the answer cites the correct subdomain. A company can have strong brand visibility while its documentation, product, or regional host remains absent from the sources that buyers follow.
Create a record for each prompt result with four fields: brand mentioned, company page cited, correct subdomain cited, and useful destination for the intended reader. Add a fifth field for wrong-host citation. A support answer that sends a prospect to developer documentation may be technically relevant but still fail the journey you intended.
Check whether different subdomains compete for the same query. Look for near-identical titles, overlapping product descriptions, and answers that alternate between hosts without a clear reason. Compare the cited URL with the page that actually explains the claim. A citation to the wrong host is not always a visibility failure, but it is a routing failure when the reader cannot complete the next step.
This distinction prevents teams from celebrating a brand mention while missing the real issue: the engine knows the company, but not which part of its site should answer the question.
Check discovery, access, and canonical signals
Check whether each intended page can be discovered, accessed, and interpreted consistently before changing its copy. Review robots directives, XML sitemaps, canonical tags, status codes, redirects, noindex rules, and internal links for every important subdomain.
Confirm that canonical URLs point to the version you want cited, not automatically to the main domain or an outdated host. Check that sitemap entries use the same protocol and hostname as the canonical URLs. Verify that pages render their essential title, description, answer, and navigation without depending entirely on client-side actions.
Search Console can reveal whether Google has indexed the intended URLs and whether Google sees a different canonical. Those checks do not prove what ChatGPT, Perplexity, Gemini, Claude, Grok, Google AI Overviews, or Google AI Mode will cite, but they expose technical inconsistencies worth fixing first. Platform documentation and engine guidance change, so review current requirements rather than relying on an old checklist.
Do not move content between subdomains during this step. First establish which signals are present, which are contradictory, and which host the business actually wants readers to reach.
Resolve duplicate and overlapping answers
Give each subdomain a distinct answer role when multiple hosts cover the same topic. Rewrite or consolidate overlapping pages only after deciding which audience and task each page serves.
Compare pages by the question they answer, not just by their keywords. A product page can explain capabilities, a developer page can explain implementation, and a support page can explain recovery. If all three lead with the same broad claims, engines may select the easiest page to quote or mix details from several hosts.
Check titles, headings, definitions, examples, feature names, plan terminology, and links across the duplicates. Keep shared facts consistent, but add audience-specific detail where it helps an engine route a question. Use cross-links that explain the relationship, such as moving from a feature description to implementation guidance, rather than linking every page to every other host.
A useful decision rule is to consolidate when two pages serve the same audience and answer the same job. Keep separate pages when the audience, action, or evidence differs. Teams already managing several product areas may also need to distinguish subdomain ownership from product ownership. See the guidance on AI visibility across product lines when those boundaries overlap.
Strengthen cross-subdomain identity and routing
Make the parent brand, subdomain purpose, and relationship between hosts explicit on every important page. Use consistent organization naming, product terminology, navigation labels, footer links, and descriptions so an engine can connect a specialist host to the company it represents.
Check whether a first-time reader can answer three questions from the page itself: who publishes this information, who is it for, and what should the reader do next? Add a concise explanation where the host name differs from the company name or where a product has its own identity. Avoid forcing readers to infer the relationship from a logo alone.
Review links in both directions. The main domain should point to authoritative specialist resources, while specialist hosts should link back to the relevant company or product context. Check that links use stable destinations and descriptive surrounding text. Do not create artificial cross-link networks or repeat identical brand copy on every page.
After changes, rerun the same prompts and compare the cited host, not just the number of brand mentions. Cituna joins answer data to Google Search Console data and provides SEO, AEO, and GEO fixes, which can help connect a routing problem in an answer with the search performance of the relevant host.
Prioritize fixes by buyer risk and evidence
Fix the subdomain errors that can mislead a buyer or block a decision before fixing low-impact citation gaps. Rank issues by the importance of the prompt, the severity of the wrong answer or destination, the number of hosts affected, and the evidence that a change is needed.
A wrong pricing, security, implementation, or eligibility destination usually deserves earlier attention than a missing citation for a peripheral article. A competitor citation on a high-intent comparison prompt also deserves review, but first confirm that your own page directly answers the comparison rather than merely mentioning the category.
Check three evidence sources before assigning work: the engine answer and cited pages, Search Console data for the relevant host, and the page’s technical and editorial signals. If the page receives search impressions but is never cited, improve answer clarity and source routing. If it is neither indexed nor cited, resolve access and canonical issues first. If the wrong host is cited, clarify ownership and cross-links before producing more content.
Track the fix by prompt and host. A single blended visibility score can hide a serious failure on a support or regional subdomain. Use a simple status such as correct host, wrong host, no brand, competitor, or no useful citation.
Retest changes across engines and subdomains
Retest every material change against the same prompts, all seven tracked engines, and the affected subdomains before declaring the problem solved. The comparison should include the original answer, the new answer, cited URLs, cited host, brand mention, and the reader’s likely next step.
Check for improvement in the intended outcome, not just more mentions. A result is stronger when the right engine names the brand, cites the right host, and sends the intended audience to a page that answers the next question. Record regressions too, especially when a new canonical, redirect, or cross-link changes which host appears.
Separate persistent issues from normal answer variation by reviewing repeated runs over time and by looking for patterns across related prompts. Do not treat one favorable response as proof that a technical or editorial change worked. Keep a change log with the date, host, URL, prompt group, reason for the change, and observed result.
Recheck after major launches, migrations, acquisitions, and domain changes. For an acquisition-specific review, use the article on AI visibility after an acquisition to cover the broader identity and ownership questions alongside this subdomain process.
Related reading
Sources consulted
- Google Search Central (developers.google.com)
- Google Search Console Help (support.google.com)
- OpenAI Platform (platform.openai.com)
- Anthropic (anthropic.com)
Drafted with AI assistance from our own research and Search Console data, and reviewed by Rahul A before publishing. Rules and prices change; check the linked official source before you act.