- Published
- Byline
- GoHighLevel Partners Editorial
- Filed under
- GoHighLevel Automation
A sitemap is a recommendation — and recommending a page you would not want a stranger to land on has consequences beyond the page.
A sitemap for funnel pages: what belongs in it and what does not
A sitemap lists the URLs on a site that you want a search engine to know about. On an ordinary website that is most of it. On a funnel-heavy site it is a much smaller subset, because a large share of the pages exist to be reached from somewhere specific — an advertisement, an email, a step before them — and have no business appearing in a search result.
Treating the sitemap as an inventory of everything is the default and the mistake. It is a recommendation, and recommending a page you would not want a stranger to land on has consequences beyond the page itself.
What to include and exclude
| Page | In the sitemap? | Reason |
|---|---|---|
| Home, services, about, contact | Yes | They answer searches and are meant to be found |
| Articles and guides | Yes | The pages most likely to earn traffic |
| Product and offer pages | Yes, where they stand alone | Someone searching the product should reach them |
| Opt-in and landing pages for campaigns | Usually not | Written for one audience arriving from one place |
| Checkout, upsell and downsell steps | No | Meaningless out of sequence, and a landing there is a dead end |
| Thank-you and confirmation pages | No | Indexing them invites visits that count as conversions |
| Test variants | No | Two near-identical URLs competing for the same query |
| Members-only pages | No | Anyone who reaches them is refused, which is a poor result |
The confirmation row matters more than it sounds. A thank-you page reachable from a search result will be reached, and each visit is counted as an outcome — the same over-counting problem described in the thank-you step, arriving by a different route.
The test-variant row is the one people forget when running a comparison. Two URLs holding near-identical content, both listed, is a request to have them treated as duplicates — worth setting up before rather than after the exercise in testing a funnel step.
The sitemap is a recommendation, not a control
Listing a page asks for it to be considered; it does not guarantee anything. Leaving a page out does not prevent it being found, either — a link from anywhere can lead a crawler to it. If a page genuinely must not appear in results, the sitemap is the wrong tool: it needs a directive on the page itself, and the two should agree.
That agreement is the check most worth doing. A page listed in the sitemap while also asking not to be indexed is a contradiction, and it is generated automatically all the time by builders that list everything by default.
Canonical addresses, and listing each page once
Every URL in the sitemap should be the canonical one: the host you chose, the scheme you serve, and no tracking parameters. A sitemap listing both the bare domain and the www version, or listing addresses that immediately redirect, is asking for the same page to be treated as several — the decision that prevents it is in choosing one canonical host, and the records underneath are in the full set of records a domain holds.
Where a page is reachable at more than one address by design — a campaign variant of a product page, for example — list the canonical one and let the page’s own canonical tag point there. The same address discipline applies to the Open Graph image on a page, which should also name the canonical host.
Keeping it accurate
- Remove what no longer exists. A sitemap full of URLs that return errors wastes crawl effort and suggests the site is not maintained.
- Keep the modification dates honest. A file claiming every page changed today, every day, teaches a crawler to ignore the field entirely.
- Skip the priority and frequency fields unless you have a reason. They are widely ignored and easy to get wrong in a way that looks deliberate.
- Split a large sitemap into a set with an index, by section, so the file stays readable and a problem can be traced to a part of the site.
- Reference it from the robots file so it is discoverable without being submitted anywhere.
Where funnel builders make this awkward
Many builders generate a sitemap automatically and list every page in the account, including the steps you would never want indexed. Check what yours produces rather than assuming, and check it again after a page is duplicated, since cloned funnels arrive complete with their checkout and confirmation steps — one more instance of the general problem in what moves and what breaks on import.
Where a blog sits alongside the funnels, its structure produces category and archive URLs of its own, and whether those belong in the sitemap depends on whether they are useful destinations — the ground covered in blog category setup on a client site.
A store adds another layer, since product pages, variants and filtered views can multiply into many near-identical URLs. List the pages a buyer should land on — the product detail page structure for each product — and keep filtered permutations out. A page whose only distinction is a filter is rarely the one you want someone to arrive at, and it will not answer the question they searched, whether that is about the product or about shipping rates at checkout.
What to check after any structural change
After a domain move, a rebuild or a bulk duplication, fetch the sitemap yourself and read it. Confirm every URL uses the canonical host, returns successfully, and is a page you would be content for a stranger to land on cold.
Then spot-check a few of the listed pages for the contradictions that creep in: a directive asking not to index, a canonical tag pointing elsewhere, or tracking added through code in the page header that assumes an entry point the visitor did not use. Those are cheap to find with a handful of manual checks and expensive to discover from a report months later — and unlike what a page speed score measures, nothing will score the sitemap and tell you it is wrong.
Frequently Asked Questions
Should funnel steps be in the sitemap?
Generally not. Checkout, upsell, downsell and confirmation pages are meaningless out of sequence, and a visitor landing on one cold reaches a dead end. Indexing a thank-you page is worse still, because each visit from a search result is counted as an outcome.
Does leaving a page out of the sitemap keep it out of search?
No. A sitemap is a recommendation, not a control — a link from anywhere can lead a crawler to a page you omitted. If a page genuinely must not appear, it needs a directive on the page itself, and the two should agree.
What is the most common contradiction in a generated sitemap?
A page listed in the sitemap while also asking not to be indexed. Builders that list every page in the account by default produce this constantly, and the combination sends conflicting signals.
Which address should be listed for each page?
The canonical one: your chosen host, the scheme you serve, and no tracking parameters. Listing both the bare domain and www, or listing addresses that immediately redirect, asks for one page to be treated as several.
Should test variants appear in the sitemap?
No. Two URLs holding near-identical content, both listed, is a request to have them treated as duplicates. Set that up before starting a comparison rather than discovering it afterwards.
What should be checked after a rebuild or a domain move?
Fetch the sitemap and read it. Confirm every URL uses the canonical host, returns successfully, and is a page you would be content for a stranger to land on cold. Then spot-check a few pages for conflicting index directives and canonical tags.
We build your GoHighLevel account for you
CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.
- Setup (one-time)$850
- Ongoing (per month)$38.80
No obligation quote · reply within 1 business day
This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.