Home/Learn/Subdomain SEO

Know which page brought each signup

Subdomain SEO carries a practical risk: splitting what search and analytics can see across your site. Put buyer-facing blogs, guides and comparison pages in folders of the main domain, and keep the app on a subdomain. Use a Search Console Domain property and analytics configured across hosts to follow the visit through to signup.

Updated November 2026

A blog or docs service offers you an address like blog.company.com. Someone warns that it will weaken your search presence. The search results offer conflicting advice, often in forum threads and videos, while the service is waiting for an address.

The useful decision starts with what people do on those pages. A guide helps a buyer find and understand your company. A logged-in app serves someone using the product. Their addresses can differ, provided the reports still connect the pages a person reads with the signup that follows.

For subdomain SEO, keep buyer pages in main-domain folders

Put the pages a potential buyer can find through search beside the product pages they lead to. That gives the blog, guides and comparisons a clear place within the main site.

A folder such as /learn can hold the questions people ask before they try the product. Those pages can link to the relevant product description, which then leads to signup. The address reflects the job of the page: helping someone understand whether the company can solve their problem.

Our own site follows that separation. Its guides sit under /learn, while the browser product runs on an app subdomain. A person can read about the work on the main site and move to the app when they want to use it. The two areas serve different parts of that visit.

For each proposed page, ask whether a buyer would arrive there from a search. If so, give it a home in the main site's folders. A public explanation of a product belongs with the pages that introduce it; the screen a customer uses after logging in has another purpose.

This also helps decide what to do with docs. A page that answers a buyer's question belongs in the same discussion as a guide or comparison. Consider what the page explains before accepting the hosting service's default address. The choice should follow the reader's reason for opening it.

Once those roles are clear, the remaining question is how the reports connect them. Keeping the app separate should still allow the company to see the public page someone read before signing up.

A subdomain blog can split one visit into two

A reader can move from your blog to your app while the reports lose the connection between those actions. Different cookie settings across hosts can make that handoff appear as a new visit.

Google's Analytics guidance describes self-referrals when visitors move between subdomains using different cookie domains. Your own site can then appear as the source of a visit. The report points to the handoff between hosts, leaving the earlier route harder to follow.

Examine the cookie settings on both hosts involved in the link. Google's guidance includes using the same cookie domain and configuring the relevant exclusions. After the settings are applied, follow a reader's path into the app and inspect what analytics recorded at that crossing.

Search Console needs a separate check of what its property covers. A property for a particular address can leave another host outside the view you are reading. Google describes a Domain property as aggregating the domain's subdomains, protocols and subpaths. That makes it a useful place to read search performance across the site.

The difference matters even when the app itself counts activity. Among early client sites we reviewed, one had analytics in the app and none on the website. The team could see activity after the handoff without seeing the pages that brought people there.

Seeing signups in the app answers only part of the question. The company also needs the public pages those people visited beforehand. Review the website and app together to see whether the reports retain the route from a guide to the signup.

A page can load at its current address while its search references still point somewhere else. Check those references alongside the links a reader uses to move between the website and app.

In an August 2026 review, a site's sitemap and canonical tags pointed to an old domain. None of its pages was in Google. Comparing the site's references with its current address exposed the old-domain entries.

For a site with several hosts, make that comparison for each host's pages. Read the addresses in the sitemap against the current public addresses. Inspect canonical tags for old-domain references too. A working link from the homepage does not establish that these separate references are current.

Menus have another job. A reader arriving on the blog needs a route to the product pages. Someone on the main site needs a route back to the guides. If the blog is hosted separately, inspect both menus after changes.

These checks answer different questions. The sitemap and canonical review examines the addresses the site supplies for search. The menu review examines the route offered to a reader. Both belong in the same host inventory, because adding or replacing a service can affect either.

For the founder, the useful output is a concrete correction list: which reference still uses an old address, or which menu lacks the relevant link. The work can then repair those entries without turning the hosting choice into a general argument about rankings.

Every new tool can add a host that nobody tracks

Adding a docs service or landing-page builder changes the route a visitor can take to signup. Someone has to notice the new address and check that analytics follows the visit across it.

The check starts with the new host's analytics tag and cookie settings. It also confirms that the relevant search data is covered by the Domain property. Then it follows the visitor through the page, the next action and the signup, using conversion tracking and funnel checks.

A founder can investigate when a number looks odd. This puts the check close to someone who knows which services were recently added. It depends on that person connecting the unusual number with the new host, inspecting the signup path and arranging the correction.

An audit can examine the hosts and identify gaps in the setup as it stands. Agree whether it includes the route to signup and the fixes it finds. Then assign responsibility for later additions, since the next docs or landing-page service may introduce another host.

People running the growth work can check measurement when they add a page or service. They know which host changed, can follow its path to signup and can make the relevant website or analytics fix. That keeps the measurement check attached to the change that created the need for it.

Compare these arrangements by those responsibilities. Who learns that a host was added? Does the check stop at a page view or continue to the signup? Who changes the tag, settings or page when the path breaks? The answers establish what the company can expect after its next website change.

A subdomain suits the logged-in app

Keep the product on a separate host when people reach it to use their account. Its address can serve that purpose while the public website handles discovery and explanation.

The app and its public product description need not occupy the same kind of address. A buyer might search for an explanation before deciding to sign up. After signup, the account screens have a different job. Separating those uses gives a practical reason for the app subdomain.

A hosting service can also constrain the choice. If a necessary blog or docs service only offers a subdomain, include that host in the site's search and measurement setup. Include the work required to connect that host when choosing the service.

Look at analytics and Search Console separately. Cookie settings and exclusions concern how visits cross between hosts. The Domain property concerns which hosts appear together in the search report. Inspect both after introducing a subdomain, then follow a visit to verify how the setup records it.

After the change, read a visit that crosses from the public page to signup. Confirm that the earlier page is still visible in the path. This is the practical test of the setup: the company can connect its published content with the action people take in the app.

Keep buyer-discovery pages in folders and the logged-in product on its own host where that fits the site. If the hosting service requires a different arrangement, include its measurement work in the choice. The company then knows which connections need attention when the service is added.

Example: finding the half of a site analytics missed

Reviews of early client sites between July and October 2026 found different gaps in their ability to count leads.

Early client siteWhat the review foundWhat could not be counted reliably
Site with an inactive analytics destinationAnalytics sent data to a dead projectThe site's own leads
Site with separate website and appAnalytics ran on the app, with none on the websiteLeads connected to the public pages that brought them
Site without analyticsNo analytics was installedThe site's own leads

The split site exposed the gap between seeing activity in the app and knowing which website page brought the visitor. Checking both hosts located that missing part of the path.

List every host your buyers pass through

  • List the public addresses

    Include the main site, blog, docs, app and any landing or booking pages that a buyer can cross before signup.

  • Open the Domain property

    Use a Search Console Domain property to read the subdomains together, then compare that coverage with the hosts on the list.

  • Connect the analytics settings

    Check cookie domains across hosts and configure the relevant exclusions, so moving within the site does not create self-referrals.

  • Follow a signup path

    Trace a test visit from a guide through to signup and confirm that analytics retains the pages along the way.

Sources

Count every visit across your site's hosts

Talk to Tin about where your pages live, what search and analytics can see, and which gap needs attention first. Our growth experiments include checking those connections as the website and its routes to signup change.

Book a call