The First 90 Days After Buying an Aged Domain

Before You Change Anything

The first 90 days after acquiring an aged domain are for establishing control, preserving evidence, and learning how search engines, users, and linking sites respond. Avoid treating the domain as a guaranteed shortcut: age and third-party metrics do not prove that rankings or historical value will transfer to a new project.

Start by saving the purchase agreement, invoice, transfer confirmation, registrar records, current DNS records, certificate details, and screenshots or exports from the tools available to you. Create a dated record of what you inherited before changing nameservers, URLs, content, or redirects.

If due diligence was limited before purchase, complete a domain-history review now. Check archived uses, ownership changes, backlink targets, trademark concerns, search-result traces, email reputation, and signs that the domain previously hosted spam or was compromised. Use the separate deindexing diagnostic if pages that should be eligible remain absent from Google.

Days 0–7: Secure and Baseline

1. Secure Domain Control

• Move the domain into an account controlled by the correct legal owner.
• Use a unique password and phishing-resistant multi-factor authentication where the registrar supports it.
• Confirm recovery email addresses, phone numbers, authorized users, and billing contacts.
• Enable registrar or transfer lock after any required transfer is complete.
• Enable auto-renew and add a monitored backup payment method, while keeping a separate renewal calendar.
• Inventory nameservers, DNS records, DNSSEC status, hosting, CDN, email, certificates, and third-party services before removing anything.

ICANN describes registrar lock—often shown as clientTransferProhibited—as a control that prevents transfer until the domain is unlocked. Our domain-registration guide covers the broader ownership and recovery setup.

2. Capture a Search and Traffic Baseline

1. Add and verify the appropriate Search Console property. Preserve access records and remove former owners only after continuity is confirmed.
2. Check Manual Actions, Security Issues, Page Indexing, HTTPS, Sitemaps, Crawl Stats, and a sample of important URLs in URL Inspection.
3. Export Search performance for the longest available comparison period, if historical data is present.
4. Install verified analytics with internal and bot traffic handled consistently. Annotate the acquisition and launch dates.
5. Save a baseline crawl containing status codes, titles, canonicals, robots directives, internal links, and redirect chains.

Google notes that crawling and indexing are not immediate and can take from days to weeks. A submitted sitemap or indexing request is a discovery signal, not an indexing guarantee. Use URL Inspection for representative pages rather than repeatedly requesting the same URLs.

3. Preserve Historical URL and Link Evidence

• Export known backlinks and referring domains from more than one source where practical.
• Export Search Console links if the property contains them, but remember that Google describes this report as a sample rather than a complete backlink list.
• Build a list of historically linked URLs from backlink exports, archives, old sitemaps, analytics, and server logs.
• Record whether each important source page and link is still live, and where the link currently lands.
• Save evidence of important historical content without republishing copyrighted material you do not own.

Days 8–30: Clean Up and Launch Carefully

4. Decide the Outcome for Historical URLs

Google recommends mapping old URLs to corresponding new locations during a move and warns against redirecting many old URLs to an irrelevant destination such as the homepage. Keep a written URL map with the evidence and reason behind each decision. Our redirect planning guide explains equivalence, chains, validation, and monitoring in more detail.

5. Launch a Coherent Site

• Publish pages that match the domain’s intended purpose and provide clear ownership, contact, privacy, and commercial information.
• Use one preferred protocol and hostname, consistent canonical tags, and crawlable internal navigation.
• Generate a sitemap containing only canonical, indexable URLs that return successful responses.
• Test mobile rendering, structured data, page titles, descriptions, image alt text, and key conversion paths.
• Check that robots.txt, page-level robots directives, authentication, and firewall rules do not block the intended public site.
• Monitor server logs and uptime during DNS and hosting changes.

Do not recreate a large historical site with thin placeholder pages simply to retain old URLs. A smaller set of complete, internally connected pages is easier to validate and more useful to readers.

Days 31–60: Observe and Correct

6. Run a Weekly Monitoring Review

• Availability: Uptime, certificate validity, DNS resolution, unexpected redirects, and server errors.
• Crawlability: robots rules, canonicals, sitemap status, crawl activity, 404s, soft 404s, and redirect chains.
• Indexation: Page Indexing reasons and representative URL inspections—not only a site: search. Record the inspected canonical, crawl status, and rendered result.
• Search performance: Clicks, impressions, queries, pages, countries, and devices, compared with the dated baseline.
• Links: Important source URLs, lost links, broken historical destinations, and referral traffic.
• Security: Search Console warnings, new administrators, software updates, file changes, backups, and suspicious pages.
• Business outcomes: Qualified visits, leads, revenue, and conversion problems.

Third-party DR, DA, traffic, and keyword estimates can help identify a trend worth investigating, but they are not Google signals or business outcomes. If a score changes, diagnose the underlying pages and links using the process in our domain metrics decay guide.

7. Respond to Evidence, Not Anxiety

• If a page is excluded, inspect the stated reason, rendered page, canonical, internal links, and content before requesting indexing.
• If an important historical backlink reaches a broken URL, restore a useful equivalent or redirect it to the closest legitimate replacement.
• If traffic falls, separate technical errors from demand, seasonality, ranking changes, measurement changes, and previous low-quality traffic.
• If Search Console reports a manual action or security issue, follow the report-specific remediation and review process. Do not assume that deleting content, changing ownership, or waiting will clear it; use the evidence-led steps in our domain penalties guide.
• Do not upload a disavow file as routine housekeeping. Google calls it an advanced feature that most sites do not need and warns that incorrect use can harm performance.

Days 61–90: Review the Acquisition

8. Compare the Site With Its Baseline

At day 90, compare like-for-like periods and document what changed. Where traffic is small, use raw numbers and avoid overstating percentage changes.

The 90-Day Checklist

• Registrar ownership, recovery, MFA, lock, renewal, and billing confirmed
• DNS, hosting, CDN, email, certificates, and administrators inventoried
• Purchase and launch dates annotated in analytics and the project log
• Search Console Manual Actions and Security Issues checked
• Baseline crawl, search performance, indexation, backlinks, and historical URLs saved
• Each important historical URL assigned a keep, redirect, remove, or investigate decision
• Robots, canonicals, sitemap, redirects, structured data, and mobile pages tested
• Important live backlinks and their destination status checked
• Weekly incidents, releases, and measurement changes documented
• Day-90 review completed using verified outcomes, costs, and limitations

Primary Sources

• Google Search Console: Why is my page missing from Google Search?
• Google Search Console: Manual Actions report
• Google Search Console: Security Issues report
• Google Search Console: Links report
• Google Search Central: Site moves with URL changes
• Google Search Console: Disavow links to your site
• ICANN: About locked domains