I run 44 websites. Not a typo. Forty-four separate properties across 15+ niches, totalling over 200,000 indexed pages. Some are WordPress, some Astro, some Next.js. Some earn money. Some don't yet.
Running this many sites has taught me things about multi-site SEO that no amount of theory could. When you manage a portfolio this size, problems don't stay isolated. They compound. A bad configuration choice on one site becomes a bad configuration choice on 23 sites. A weak title tag template doesn't cost you clicks on one page: it costs you clicks on 2,376 pages.
This post covers what actually happens when you manage SEO across multiple websites, and the systems I've built to keep it under control.
The Three Problems Nobody Warns You About
Most guides to multi-site SEO focus on the obvious stuff: separate Google Search Console properties, different hosting, distinct branding. That's table stakes. The real problems are harder to spot.
1. Your Own Sites Fight Each Other
When you own multiple sites in overlapping niches, Google doesn't know they belong to the same person. It treats them as competitors. If two of your sites target "best cordless vacuum" with similar content depth, Google picks one and suppresses the other. You've spent twice the effort for the same result.
This isn't theoretical. I've watched it happen in my own portfolio. The fix is keyword territory mapping: assigning distinct keyword clusters to each site so there's zero overlap. Site A owns "robot mowers." Site B owns "cordless lawn care." They serve the same broad niche but never chase the same query.
2. Technical Mistakes Replicate Across Every Site
This is the one that hurts most. When you build sites from shared templates or follow the same setup patterns, a single configuration error propagates everywhere.
In my own technical SEO audit across the portfolio, I found three issues appearing across the majority of sites:
- Canonical URL splitting: 23 of 44 sites had Google indexing both trailing-slash and non-trailing-slash versions of the same pages
- Title tag truncation: 8 sites had programmatic titles exceeding Google's 55-60 character display limit
- Index bloat: 31 sites had pages in Google's index that shouldn't have been there (tag archives, parameter URLs, thin pagination pages)
These problems recur when sites are built without a centralised quality check. The 23 sites got there by different routes: missing Astro trailing-slash config on some, Next.js routing inconsistencies on others, WordPress permalink settings clashing with CDN cache rules on the rest. Different stacks, same underlying pattern: internal links not matching the canonical URL format.
The upside? When you fix the root cause, you fix it everywhere. One template change on wagearea.com updated 2,376 pages simultaneously. That's the return portfolio SEO gives you when the fix applies across the template, not to a single page.
3. You Can't Give Every Site Enough Attention
Forty-four sites means roughly 3.9 hours per site per month if I worked full-time (173 hours a month) on nothing else. That's not enough for content creation, technical maintenance, topical authority work, and performance monitoring combined.
The honest answer: not every site deserves equal attention. Some get 20 hours a month. Some get 20 minutes. The difference is a prioritisation system based on data, not gut feeling, weighted toward the sites where topical authority is still being built.
How to Prioritise Which Sites Get Attention
I score every site across four dimensions:
- Revenue potential: Is this site in a monetisable niche? Does it have affiliate, ad, or lead-gen potential?
- Search volume: What's the total addressable search volume for this site's keyword territory?
- Technical health: How many critical issues does the site have right now?
- Competitive position: Is this site on page 1 for its target queries, or page 5?
A salary data site with 7,733 monthly impressions, 1,546 page-one rankings, and a fixable title truncation problem scores higher than a brand-new site with zero impressions and no obvious technical issues. The first site has latent value locked behind a template fix. The second needs months of content investment before anything moves.
This is why I fixed wagearea.com's titles before touching newer sites. One mapping function, shortOccName(), converted verbose government job classifications into search-friendly titles. Daily impressions jumped from 383 to 898 within 5 days. A 134% increase from a single template change.
That's the kind of ROI you chase in a portfolio: outsized return, low effort, immediate impact.
Keyword Cannibalisation Across a Portfolio
Cannibalisation between your own sites is different from cannibalisation within one site. When two pages on the same domain target the same keyword, Google picks the one it thinks is best. When two separate domains you own target the same keyword with genuinely overlapping intent, you're paying for content, hosting, and maintenance on both while only one captures the ranking value.
How to Detect Cross-Site Cannibalisation
Pull your Google Search Console data for all properties. Export the queries each site ranks for. Look for overlaps. If site A and site B both appear in GSC data for the same query, that's a candidate for cannibalisation, not proof of it: two sites can both rank for an overlapping term without meaningfully competing, especially if the intent behind the query differs. Confirm it before acting: check whether combined impressions or clicks for that query are falling, whether one page is suppressing the other in the SERP, or whether the two pages are genuinely chasing the same search intent.
I use a centralised GSC monitoring setup that pulls data from all 44 properties into one view. When the same query appears for multiple sites, I flag it and decide which site should own it based on:
- Which site has stronger topical authority in that area
- Which site has more supporting content around that topic
- Which site has better technical health and faster page speed
Once that's confirmed, not before, the losing site gets a noindex on that specific page, or I rewrite the content to target an adjacent keyword instead. Overlap on its own isn't enough to justify either move.
This only works at scale because I am not checking 44 GSC properties one at a time. Query-level data from every property lands in a single view every week, so a cross-site match that Google would otherwise arbitrate silently shows up as a flagged row before it costs six months of two of my own sites competing for the same SERP slot. On one site, manual checking is fast enough to do by eye. Across 44, the exact kind of conflict it exists to catch is two sites in adjacent niches, say a salary-data property and a careers property, both drifting onto the same job-title query without me noticing until rankings for both flatten out.
How to Prevent It
Prevention is simpler than detection. Before creating content on any site, I check whether another site in the portfolio already targets that keyword. Each site has a defined keyword territory document. If a keyword falls outside that territory, it doesn't get published there, regardless of how tempting it looks. Turning down a plausible page on the wrong site is cheaper than winning a ranking fight against myself six months later.
When to Merge vs Keep Separate
This decision costs portfolio owners more money than almost any other SEO choice.
Merge when:
- Two sites target the same niche and the same audience
- Neither site has enough content depth to build topical authority alone
- You're splitting backlinks and brand mentions between them
- Maintaining both costs more than the combined traffic justifies
Keep separate when:
- The sites serve genuinely different niches (a pet products site and a calculator tool have nothing in common)
- Each site has distinct keyword territories with no overlap
- The audiences are different even if the broad topic is similar
- One site is location-specific and the other is national/global
I've made both decisions in my portfolio. Sites that covered overlapping product review categories got consolidated. Sites in completely separate verticals, such as energy data, salary information, and health products, stayed independent because merging them would dilute topical relevance and confuse Google about what the combined site was actually about.
Manage each domain as an independent SEO project with its own topical territory. The moment one site starts covering another's niche, you dilute the topical relevance of both, and Google struggles to work out what either one is actually about.
That's the principle, not a rule about domain count: a portfolio of ten sites with clean topical boundaries beats three sites with blurred ones every time.
The Systems That Make Multi-Site SEO Manageable
Running 44 sites without systems would be chaos. Here's what I actually use:
Centralised GSC Monitoring
Every site connects to Google Search Console through a service account. I pull 28-day snapshots across all properties and flag sites where impressions drop more than 15%, CTR falls below niche benchmarks, or new crawl errors appear.
This takes the "check all 44 sites manually" problem and reduces it to "review the flagged sites." On a typical week, 5-8 sites need attention. The other 36+ are fine.
Templated Technical Audits
Every technical audit follows the same checklist: canonical configuration, index coverage, title tag lengths, Core Web Vitals, internal link structure, sitemap accuracy. Running the same checks in the same order means I catch the same issues faster.
When I find a new issue type, like the trailing slash problem, I add it to the technical SEO audit template and retroactively check all 44 sites. That's how I discovered 23 sites had the same canonical splitting issue. Without a systematic approach, I'd have found it on one site and assumed it was isolated.
Scheduled Rebuilds
Twelve of my Astro-based sites run weekly automated rebuilds via GitHub Actions every Monday at 06:00 UTC. This ensures sitemap freshness, catches build errors early, and keeps deployment pipelines tested. If a rebuild fails, I get notified before Google notices anything wrong.
Systematic Title Frameworks
Every programmatic site follows a title tag framework designed to stay under 55 characters. The framework accounts for the longest possible dynamic insertion (city name, job title, product name) and truncates gracefully. No more discovering three months later that 800 pages have broken titles because someone added a suffix to the template.
Resource Allocation: The Honest Numbers
Here's what multi-site SEO actually requires in terms of time:
- High-priority sites (strong revenue, fixable issues): 15-20 hours/month each
- Growth-phase sites (building content, no revenue yet): 8-12 hours/month each
- Maintenance sites (stable traffic, earning revenue): 2-4 hours/month each
- Monitoring-only sites (coasting, minimal intervention): 30 minutes/month each
The unfair advantage of running 44 sites instead of four is that the fixed cost of a system amortises across every property it touches. Building the centralised GSC dashboard, the technical audit template, and the keyword territory documents was expensive once. Applying each of them to the next site is close to free. A consultant running four sites pays roughly the same build cost for about a tenth of the payoff, since four sites is one-eleventh of a forty-four-site portfolio, not a quarter of it. That asymmetry, not any single tactic, is the real advantage of managing a portfolio this size: the marginal hour spent on site 44 buys more than the marginal hour spent on site 4 ever could, because the systems it draws on are already paid for.
Most of my 44 sites fall into the last two categories. That's the goal. Build a site, optimise it, get it earning, then move it to maintenance mode so you can focus energy on the next high-potential property.
If you're thinking about running multiple sites, be realistic about the time commitment. SEO takes months to show results on a single site. Across a portfolio, you need patience multiplied by the number of properties, and the discipline to avoid spreading yourself so thin that nothing gets enough attention to succeed.
The Portfolio Advantage
Despite the complexity, managing multiple websites has one massive advantage over managing one: pattern recognition at scale.
When you see the same SEO mistake on 23 of 44 sites, that's a systemic issue, not a one-off. When a title tag fix produces a 134% impression increase on one site, you can apply the same fix to 7 other sites with the same problem and reasonably expect similar results.
Single-site SEO gives you anecdotes. Portfolio SEO gives you data.
The trailing slash fix on sunnypatel.co.uk, landing alongside separate page-pruning work in the same window, moved average position from 31.6 to 25.6. I then applied the trailing-slash fix to 22 other sites. That's the compound return of managing SEO across multiple websites: every lesson learned multiplies across the entire portfolio.
