Discussion
  • Content SEO

Do YMYL sites take longer to recover rankings after domain migrations than non-YMYL sites, in your experience?

Published 1 reply

Discussion starter: a YMYL 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

    I am not aware of a public dataset that compares migration recovery times for YMYL and non-YMYL sites, so any answer is based on reasoning and practitioner experience rather than measurement. The reasoning points one way: YMYL rankings depend heavily on trust and reputation signals, and anything that disrupts how Google connects those signals to the site, such as a domain change, lost author and reviewer information, broken references or changed content, can take longer to settle. A well-executed migration that keeps content, authorship and structure intact and redirects every URL properly should not recover much more slowly for a YMYL site. A migration that changes many things at once is riskier for a YMYL site, because more of what supported its rankings is in play.

    Why YMYL migrations carry more risk

    • Trust signals are more important. Google says its systems give more weight to expertise and trustworthiness on health and finance topics, so any loss of those signals matters more.
    • Author and reviewer information is often lost. Migrations that drop bylines, reviewer credits, review dates or author pages remove visible evidence of expertise.
    • Content is often “refreshed” during migrations, changing pages that were performing well.
    • External references matter. Links from institutions and publications need to redirect correctly, and profiles elsewhere need updating to the new domain.

    Preserve what supports YMYL rankings

    Element What to preserve
    Author and reviewer information Bylines, reviewer credits, credentials, review dates and author pages, at equivalent URLs
    Content Same content at launch; improvements after the migration has settled
    Structured data Organization, Person, Article and medical or financial markup where used
    Trust pages About, editorial policy, review process, contact, complaints and regulatory information
    Redirects One-to-one for every URL, including author pages, PDFs and old URLs with links
    External profiles Updated links on professional directories, regulators’ listings and social profiles

    Reduce the number of changes

    The single most effective risk control is to change one thing at a time: move the domain or platform with content and structure intact, let it settle, then improve content and design. Google’s site move guidance describes how signals transfer through proper redirects, and it also notes that changes made at the same time can make the move harder to process. For a YMYL site, where rankings rest on accumulated trust, a like-for-like move followed by improvements is the safer path.

    Hypothetical example:

    Two health publishers migrate in the same year. The first moves to a new domain with identical content, author pages and reviewer credits, redirects every URL and updates its profiles on professional directories; its traffic dips for a few weeks and returns to previous levels within about two months. The second combines a domain change with a redesign that drops reviewer credits from article templates and merges author pages into a single “our team” page; its traffic falls further and has not fully recovered six months later. The difference is not that one is YMYL and the other is not; both are. It is how much of what supported their rankings was changed.

    Watch for this:

    Migrations are often used as an opportunity to remove “old” content. On YMYL sites, older, well-maintained pages may carry significant links and trust. Decide on pruning separately, with data, after the migration has settled.

    Set expectations with stakeholders

    YMYL organisations are often risk-averse, and a traffic dip after migration can cause alarm. Before launch, agree what normal fluctuation looks like, how long it may last, and which signals would indicate a real problem, such as sections not recovering after several weeks, important pages not indexed on the new domain, or redirects failing. Share the monitoring plan and a timeline of expected milestones. That turns an uncomfortable period into a managed process, and it gives the team room to diagnose calmly if something does go wrong.

    Monitoring after the move

    Track clicks and impressions by section, the Page indexing report for the new domain, redirect behaviour in logs, and rankings for the site’s most important YMYL queries. Check that author pages and trust pages are indexed on the new domain. If some sections recover more slowly, compare what changed for those sections specifically. For domain moves, use Search Console’s Change of Address tool as Google’s site move documentation describes.

    Treat YMYL migrations with extra caution, not because recovery is inherently slower, but because more is at stake: preserve authorship, reviewer information, trust pages and content, redirect everything, change one thing at a time, and make improvements only after the move has settled.

    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.