Marketing & search · Practical guide

Keep preview addresses out of the public search inventory

The generated inventory uses a build environment's base URL. Public submission therefore advertises preview addresses.

Healthcare marketing calendar, campaign materials and a laptop showing anonymous charts.
Help the right people find your service and take a useful next step.

What to change

The inventory's website domain must come from an approved production setting, not whichever environment happened to build it. Ask for a simple check listing every distinct website domain in the output before release. A preview build is a useful challenge case because it reveals whether temporary settings leak into publication files. The final evidence should confirm the correct origin for all entries, including newly added nested resources.

A worked example

Illustrative example

Illustrative test: Build using a preview environment and inspect the resulting sitemap before release. Include a newly added guide in the sample because older entries may use a different configuration source. A preview build may accidentally produce a sitemap whose entries all use the temporary preview domain. The supplier's release check lists distinct domains and flags the mismatch before publication. Your team confirms the intended live domain and reviews a newly added deep guide after correction. This shows that a valid-looking inventory can still be wrong in substance and that the check covers new content as well as older entries.

Healthcare SEO research with a search-results page, inspection lens, location pin and service card.
Match a useful service page to the searcher's task.
Healthcare technical SEO illustrated by a page hierarchy and connected internal links.
Give visitors and crawlers clear routes through the website.

What this means for your practice

A sitemap can be correctly formatted yet describe the wrong website. If a build picks up its preview address, search engines may be directed to unfinished copies instead of the public guides. Ask your supplier to show every website domain present in the generated inventory before publication. The practice should confirm the approved live domain and any deliberate exceptions. Include a newly added nested guide in the sample, since old entries may come from a different source. Testing a preview build is useful precisely because it challenges whether temporary settings can leak into public files. The release check should flag that mismatch before the inventory is submitted or published.

How to check the result

Every submitted URL belongs to the intended production origin.

A mistake to avoid

A valid XML document can still describe the wrong website.

Turn reading into a next step

Your action checklist

Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.

Checks to discuss

Record what you know, what is still missing and the answer you need from your team or supplier.

Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.

Further reading

These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.

Related guides

Need help with this?

Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.

Explore marketing & search services or discuss your project.

Try the free Healthcare Digital Planner to find your starting priority.