Discussion
  • Site Architecture
  • Technical SEO

Moving a blog from a subdomain to a subfolder: has anyone seen gains that clearly weren’t just the link, template and content clean-up done during the move?

Published 1 reply

Discussion starter: a technical SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.

Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.

1 reply

  • admin
    Admin
    Original poster

    Clean public evidence is scarce. Most published cases of gains after moving a blog from a subdomain to a subfolder involved other changes at the same time: better internal linking from the main site, a new template, content pruning, fixed technical problems, or links repointed during the migration. Google has said for years that it does not inherently prefer subfolders over subdomains, and that it can treat subdomains as part of a site or separately depending on how they are set up. So a move can help, particularly where the subdomain was operated like a separate site, but I would not promise gains from the location change itself, and I would do the clean-up work whether or not the blog moves.

    Why the evidence is so muddy

    • Migrations bundle changes. Teams rarely move a blog without also redesigning it, pruning it and linking it better.
    • No control group. There is usually one blog and one move, so seasonality, updates and competitor changes cannot be separated.
    • Survivorship. Moves that produced gains are written up; moves that produced nothing or a loss are quietly forgotten.
    • Short time frames. Case studies often report the first few months, when migration noise is highest.

    Plausible mechanisms, and what they depend on

    Mechanism When it plausibly helps
    Shared site-level signals If the subdomain was being assessed as a separate site with weaker signals than the main domain
    Integrated internal linking If the move leads to real links between blog content and product pages in both directions
    Operational consistency If the subdomain ran a different CMS, template quality or analytics set-up with problems
    Consolidated links If external links to the blog start supporting the main site’s commercial pages through internal links

    Each of these depends on specifics. A subdomain that already shares navigation, design and cross-linking with the main site may gain little from moving.

    If you want to isolate the effect

    The only way to learn much is to change the location and nothing else, which is rarely practical. The next best approach is to separate the steps: first improve internal linking, templates and content on the subdomain and measure; then move to the subfolder with like-for-like URLs and redirects, and measure again, with another section of the site as a rough comparison. If the second step adds a clear, sustained improvement beyond the first, you have evidence about the location itself. Most teams will not do this, because the migration is usually justified on operational grounds anyway.

    Reasons to move that do not depend on rankings

    • One CMS, one template system and one set of release checks.
    • Simpler analytics and attribution without cross-domain tracking.
    • Easier linking between editorial content and product pages.
    • Fewer hostnames to secure and monitor.

    If those benefits are real for your team, the move is worth doing on those grounds, with any search gain treated as a bonus.

    Hypothetical example:

    A software company’s blog lives on a subdomain running an old CMS with slow templates and no links to product pages. It first adds contextual links from blog posts to relevant features and from features to guides, fixes templates and prunes outdated posts, all on the subdomain. Blog traffic and demo requests from the blog rise over the next quarter. It then migrates the blog to a subfolder with one-to-one redirects and no other changes. After the migration settles, performance is similar to before the move, with a small improvement that is within normal variation. The team concludes that most of the gain came from the clean-up, and that the move’s main benefit is running one CMS.

    Watch for this:

    A subdomain-to-subfolder move is still a migration. Redirect every URL to its equivalent, update internal links and sitemaps, keep redirects long term, and expect some fluctuation. Poorly executed moves cause losses that no structural benefit makes up for.

    What to monitor after the move

    If you do move, watch the signals that tell you whether Google has processed the migration before judging the outcome. In logs, Googlebot should follow the redirects from the subdomain and start requesting the new subfolder URLs; the redirect hits taper off over weeks. In Search Console, the old subdomain property should show falling impressions while the main property picks up the same queries on the new URLs, and the Page indexing report should show the old URLs as “Page with redirect”. Compare clicks for the blog section as a whole against the same period a year earlier, and against another section of the site that did not move, rather than against the weeks immediately before the migration. Judge the result after three to six months, once the transition noise has settled.

    How to set expectations

    Tell stakeholders that the move will simplify operations, that search effects are uncertain and may be neutral, and that the most reliable gains come from integration and quality work, which you will do regardless. If a gain appears, report it with its confounders. If it does not, the project still delivered what it promised.

    Do the linking, template and content work first because it is where the evidence points, move the blog if the operational case is sound, and treat any ranking gain from the location change itself as unproven.

    Need help with this on your own site?

    Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.

    See SEO services

Add a reply

Replies are open to approved members. Log in or apply to join.