When to Fix, Add or Merge Microsites in Your Network

Before anyone registers another domain, we answer four questions. Who's the customer, what are they trying to do, which service fits and what's the next step? Then we find the page that already serves that need, and we weigh the new site against improving your main website. The brief says what's missing, which problem the new site would solve and why a separate site would make it clearer.

A new branch with a different service process may need information that the current portfolio does not provide. Another city name attached to an otherwise identical form does not by itself establish a new purpose. The brief should make that difference visible before design begins.

The separate website decision guide covers whether to build a separate site at all. This guide picks up once you have several sites competing for upkeep. Counting them won't tell you which one to fix next.

Each row is a place to start looking. Low traffic can have several causes, so we note what's still uncertain and name the next check before anyone reads too much into one number.

Review query intent, impressions, clicks, destination and device where the data supports the view. A page appearing for an unrelated meaning of a trade term needs different work from a page appearing for the intended service but failing to explain the offer.

Search Console defines its search performance measures. Keep those measures separate from qualified inquiries. An average position is an aggregate observation; it does not describe one fixed result that every customer sees.

Then compare your inquiry records with the search data. A quiet page may answer one high-value customer question, while a busy one draws people your service doesn't fit. Given the choice, we'd keep the quiet page that answers a real buyer's question. The owned lead measurement playbook keeps both views without pinning guessed revenue on impressions.

Require information that the destination can maintain responsibly: a real service process, authorized project evidence, decision tools, product scope, or audience specific preparation. A market page should explain actual service coverage and useful local context when supported, without pretending a business has a physical office in every location.

Google's spam policies address doorway pages and scaled low value content. So we hold every site to one test: it has to be useful on its own, with clear menus and a real business purpose.

We don't build a separate page for every wording of organic, SEO, exclusive and branded leads when one page can answer the same buying decision. Use language customers recognize within the appropriate page. A different question, evidence set, or action is a better reason for another resource.

Group sites by launch period and the length of time they have been usable. A group launched early in the year has a different observation window from a group launched recently. Keep sites that remain blocked, incomplete, or unavailable visible rather than silently dropping them from the inventory.

Show the number of sites, live dates, valid inquiries, qualified opportunities and known attribution gaps for each group. Where useful, calculate an explicitly labeled rate per active month, while recognizing that early performance and seasonal demand may not behave linearly.

We count our own networks this way. When Jeff Clerisier, our founder, checked the inquiry count for a residential roofing network we run in Indiana, he left the sites added later out of the original group. The microsite cohort report explains those denominator and timing choices, and why one portfolio average can't describe every site or prove new demand by itself.

When two destinations serve the same audience and task, compare their content, evidence, links, active inquiries, and operational dependencies. Merging can make the content easier to maintain and use, but first we check what each site brings in today.

Preserve useful material and map each affected URL to a relevant destination before changing the live experience. Review forms, phone routing, campaign destinations, business references, and ownership responsibilities. A domain used in printed materials or customer communication may need continued operational attention even after its content moves.

Google's site move guidance recommends a URL mapping and monitoring process. The existing content consolidation guide develops that implementation decision. We don't delete a live site without a reviewed plan for that specific change.

A page can support several discovery channels. Paid traffic may provide useful feedback on the offer when the campaign and measurement are appropriate, but it does not validate an organic ranking forecast. Organic visibility can inform questions worth testing without proving that an ad campaign will be profitable.

Clear answers also support the way people compare services through AI tools. Treat AEO and GEO as part of the information quality review: specific questions, supported facts, readable explanations, and appropriate next steps. Do not use an AI label to justify duplicate content or promise a citation.

Record which resource is being improved, expanded, monitored, or considered for consolidation. Assign an owner, the needed evidence, and the next review condition. Preserve the decision rationale so later results can be understood against the original assumptions.

For example, a hypothetical window portfolio might pause new domains while the team creates approved installation evidence and repairs a confusing consultation form. A separate resource for commercial projects would remain a candidate until the business confirms that service scope and the content it can support. The plan follows the constraint instead of treating expansion as the default.

Request a microsite portfolio review with the current domains, launch dates, search exports and inquiry stages. Trojan can turn that inventory into a practical sequence of improvements and a better grounded expansion discussion.

Should every keyword have its own microsite?

No. Similar phrases may describe the same customer task. Give that task a strong destination and create another only when its audience, evidence or useful action is distinct.

Does a low traffic site need to be removed?

Not automatically. Check its age, accessibility, search intent, customer purpose, qualified inquiries and operating dependencies before deciding what to change.

Does consolidation guarantee stronger rankings?

No. It can improve organization and maintenance when resources overlap, but search results remain uncertain. Plan the move, preserve relevant information and monitor the outcome.

How should a national company prioritize markets?

Start with actual service capacity, customer demand evidence, competitive context and the resources needed to maintain useful information. A national strategy does not require identical pages for every place.