Switching from .org to .com: A Step-by-Step SEO Migration Plan

A charity becomes a social enterprise. An association launches a paid membership arm. A non-profit simply wants the .com that everyone types by mistake. Whatever the reason, moving a long-established site from .org to .com puts years of rankings on the line, and the agency running the site carries the risk.

Done carefully, the move keeps almost all of that value. Google can transfer rankings, backlinks and indexed pages to the new domain as long as every old address leads to its new home with a permanent redirect. This plan sets out the work in ten steps across four phases, with redirect rules you can adapt and the checks to run on either side of launch.

Will switching from .org to .com affect rankings?

Yes, for a while. Google has to recrawl the old URLs, follow the redirects and move its signals to the new addresses. Its site move guidance warns that visibility can fluctuate during that time, so a few rough weeks do not mean the project has failed.

Expect some or all of the following early on:

• Positions and organic traffic moving up and down.
• Old .org URLs lingering in search results.
• New .com URLs gradually taking their place.
• Indexing reports shifting between the two Search Console properties.

Is .com better than .org for SEO?

No. Google classes both as generic top-level domains with no built-in ranking advantage and no link to a country. The choice is about audience: .com reads as commercial, .org reads as a charity, association or public body. Decide on that basis, then protect what the site has already earned.

Can a site that is ten years old keep its rankings?

Most of them, yes. Search value lives in the pages, the content and the links pointing at them, not in the domain name. Google treats a 301 redirect as a strong sign that the new URL should replace the old one. Nobody can promise every position survives unchanged, though, and age alone guarantees nothing.

Take a trade association with 400 indexed pages, a library of PDF reports and a decade of links from industry press. Launch a new .com without connecting the old URLs and Google sees a brand-new site with no history. Redirect every old page to its match and that history comes along.

What needs protecting during the move?

Anything people or search engines reach through the old domain: page URLs, content, backlinks, downloads, subdomains and email. Each one needs a plan before launch day.

Asset	Risk if missed	How to protect it
Page URLs	404 errors and lost rankings	Keep the same paths on .com and redirect page to page
Content	Google treats pages as new rather than moved	Keep titles, headings, copy and structured data unchanged during the move
Backlinks	Links from other sites hit dead pages	Redirect every linked URL, then ask key sites to update
PDFs and images	Downloads and image traffic vanish	Add media URLs to the redirect map
Subdomains	Portals and booking systems break	Plan each subdomain separately; the main redirect does not cover them
Email on .org	Mail stops arriving after DNS changes	Leave the .org MX records alone until email has moved

Change one thing at a time. Google recommends spacing out site changes, so avoid launching a redesign or a new URL structure alongside the domain move. If both are unavoidable, our website migration service can plan the order.

Phase 1: Prepare (steps 1 to 4)

Most migration problems are created here, and they are far cheaper to fix now than after launch. The aim is a baseline, a backup, a checked new site and a complete redirect map.

Step 1: Record a baseline

You need numbers to compare against later. From Google Search Console, GA4 and a crawler such as Screaming Frog, collect:

• Every indexable URL, plus existing redirects and broken pages.
• Sixteen months of clicks, impressions and top queries from Search Console.
• Positions for the client’s most important terms and the top organic landing pages.
• The most-linked pages, from Search Console’s Links report or a backlink tool.
• Canonical tags, sitemap URLs, images, PDFs and other downloads.

Step 2: Back everything up

Take a full copy of the database, files, media, themes, plugins and configuration, and store it away from the live server. Export or screenshot the DNS records as well, including MX records, SSL settings and connected services such as payment gateways, CRMs and booking tools.

Step 3: Build and check the .com site

Stand the new site up on staging and check it before any redirect goes live:

• Valid SSL on both example.com and www.example.com.
• No noindex tags and no “Disallow: /” in robots.txt on the live .com site.
• Canonical tags pointing at .com URLs.
• Internal links, images and downloads using the .com address.
• Working forms, navigation and an XML sitemap of .com URLs.

On WordPress, update the WordPress Address and Site Address under Settings > General, then replace the old domain throughout the database. WP-CLI handles serialised data safely, and a dry run shows what will change first:

# See what would change
wp search-replace 'https://example.org' 'https://example.com' --all-tables --dry-run

# Run it for real (after a database backup)
wp search-replace 'https://example.org' 'https://example.com' --all-tables

Some page builders store URLs in their own format, so check a few pages by hand afterwards. If the database work is outside your team’s comfort zone, our white-label WordPress developers can handle it.

Step 4: Build the redirect map

A redirect map is a spreadsheet pairing each important old URL with its new destination. Where paths stay the same, one domain-wide rule covers them. Any URL that changes gets its own row.

Old URL	New URL	Status
https://example.org/	https://example.com/	301
https://example.org/about-us/	https://example.com/about-us/	301
https://example.org/membership/	https://example.com/membership/	301
https://example.org/news/old-title/	https://example.com/news/new-title/	301 (path changed)
https://example.org/files/annual-report.pdf	https://example.com/files/annual-report.pdf	301

Send each old page to its closest match. Redirecting everything to the homepage throws away the value of deep pages, and Google may treat those redirects as soft 404s.

Phase 2: Launch the redirects (steps 5 to 7)

Two rules do most of the work: one on the old .org domain that forwards every request to the same path on .com, and one on the .com site that sends all traffic to a single preferred version. On Apache both live in .htaccess; Nginx needs the equivalent server block.

Step 5: Redirect the .org domain

For Apache with mod_rewrite, add this to the old domain’s .htaccess. On WordPress, place it above the “# BEGIN WordPress” block, and swap in your own domains.

# Send every .org URL to the same path on .com
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTP_HOST} ^(www\.)?example\.org$ [NC]
RewriteRule ^ https://example.com%{REQUEST_URI} [R=301,L,NE]
</IfModule>

The rule covers both example.org and www.example.org, keeps the path and returns a 301. Query strings carry across automatically. It only works when paths match on both domains, so put any changed URLs above it as individual redirects.

On Nginx, the equivalent goes in the old domain’s server block:

server {
    listen 80;
    listen 443 ssl;
    server_name example.org www.example.org;
    # ssl_certificate lines for example.org go here
    return 301 https://example.com$request_uri;
}

Keep the old domain’s SSL certificate valid. If it expires, anyone following an old https link sees a security warning before the redirect can run.

Step 6: Choose one version of the .com

Pick a single preferred version, such as https://example.com without www, and redirect the rest to it. On Apache:

# Send www and http traffic to https://example.com
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTP_HOST} ^www\.example\.com$ [NC,OR]
RewriteCond %{HTTPS} !=on
RewriteRule ^ https://example.com%{REQUEST_URI} [R=301,L,NE]
</IfModule>

Two set-ups need extra care:

• Both domains in one folder. Put both rule sets in the same .htaccess, with the .org rule first.
• Cloudflare or another proxy. If HTTPS ends at the proxy, the %{HTTPS} check can loop. Use the proxy’s redirect rules or the host’s HTTPS setting instead.

Back up .htaccess before every edit. One typo can take the site down with a 500 error.

Step 7: Test every redirect

Run the redirect map through Screaming Frog in list mode, spot-check in a browser, or use curl:

# Check a single URL
curl -I https://example.org/membership/

# Show every hop in the chain
curl -sIL http://www.example.org/membership/ | grep -iE "^HTTP|^location"

A pass looks like one 301 with a Location header for the .com URL, then a 200. Test http and https, with and without www, a deep page, a URL with a query string, a PDF and the .com variants. Google follows up to ten redirect hops, but each hop slows visitors down, so aim for exactly one.

Phase 3: Tell Google (steps 8 and 9)

Once the redirects are live, make every signal on the new site agree, then file the move in Search Console. The Change of Address tool supports the redirects; it does not replace them.

Step 8: Update canonicals, links and sitemaps

• Canonicals: every .com page should point to itself, for example <link rel=”canonical” href=”https://example.com/membership/” />. None should mention .org.
• Internal links: menus, buttons, footers and in-text links should use .com URLs directly instead of relying on redirects.
• Sitemap: submit the .com sitemap in Search Console. Google says the old sitemap can be removed.
• Robots.txt: do not block the old domain. Google needs to crawl old URLs to see the redirects.
• Tracking and ads: update the GA4 data stream, Tag Manager triggers and ad final URLs.

Step 9: File a Change of Address

Google’s Change of Address tool tells Google that a whole domain has moved. Check the requirements first:

• You must be a verified owner of both properties, signed in with the same Google account.
• It covers domain-level moves only, not http to https, www to non-www or single pages.
• The old homepage must already 301 to the new homepage.

1. Verify both the .org and .com domains in Search Console.
2. In the old .org property, open Settings > Change of address.
3. Choose the new .com property.
4. Let Google run its checks and fix any critical failures.
5. Submit the request.
6. Keep monitoring both properties. Google says the move signal lasts 180 days.

If the client uses Bing Webmaster Tools, its Site Move tool does the same job for Bing and Copilot.

Phase 4: Monitor and tidy up (step 10)

Compare the new site with the step 1 baseline page by page, not just in total. Watch indexing, redirects, rankings, referral traffic and enquiries, and move the most valuable backlinks to the new domain directly.

Step 10: Update backlinks and listings

Ask the sites behind the strongest backlinks to switch to .com, then update everything the client controls:

• The Google Business Profile website link, which matters for local SEO.
• Social profiles and directory listings.
• Email signatures, PDFs and printed material.
• Ad campaigns, landing pages and email templates.

What to watch	Where	Good looks like
Indexing	Search Console > Pages (.com)	.com pages rising, .org pages falling
Redirect errors	Crawler and 404 reports	No 404s on old URLs that had traffic or links
Canonicals	URL Inspection	Google picks the .com URL
Rankings and clicks	Search Console > Performance	Back near baseline once settled
Enquiries	GA4 conversions	Steady organic leads

Seasonality, competitors and algorithm updates move traffic too, so compare like-for-like periods before blaming the migration.

How long does a .org to .com migration take?

There is no fixed answer. Google’s documentation says a small to medium-sized site can take a few weeks for most pages to move, and larger sites take longer, depending on URL count, server speed and crawl frequency. For big or complex sites, read Google’s full guide to site moves with URL changes.

Should the old .org domain be kept?

Yes. Google advises keeping redirects for as long as possible, generally at least a year. With a decade of links, bookmarks and printed references, permanent is safer. Letting the .org expire is a real risk: someone else can buy it, inherit its links and impersonate the organisation.

Subdomains such as portal.example.org or shop.example.org are not moved by the main redirect or the Change of Address tool. Each has its own logins and integrations, so plan them separately, and sometimes leave a critical one in place until later.

Common migration mistakes

Mistake	Result	Prevention
No 301 redirects	Old URLs return 404	Domain-wide rule plus a redirect map
Everything sent to the homepage	Deep pages lose their value	Page-to-page redirects
Canonicals left on .org	Mixed signals slow the move	Self-referencing .com canonicals
Redesign launched at the same time	No way to tell what caused a drop	Move first, redesign later
PDFs and images forgotten	Downloads break	Media URLs in the map
New site blocked from Google	Pages never get indexed	Check robots.txt and noindex before launch
Old domain cancelled	Links and bookmarks die	Renew it and keep the redirects
No monitoring	Problems found after traffic has gone	Weekly checks for three months

Frequently asked questions

Can a site move from .org to .com without losing SEO?

Most of its value, yes. Page-to-page 301s, unchanged content, updated canonicals and a Change of Address request help Google carry rankings across. Expect short-term movement, and be wary of anyone promising identical rankings.

Do 301 redirects pass link value to the new domain?

Yes. Google’s Gary Illyes said in 2016 that 30x redirects no longer lose PageRank. It works best between equivalent pages, not for mass redirects to the homepage.

How long should the redirects stay in place?

At least a year, Google says, and permanently for an established site. Keep the old domain registered so nobody else can use its links.

Does .htaccess need editing on both domains?

Usually. The old domain needs the rule that forwards to .com, and the new one needs the rule that settles on one preferred version. Nginx servers ignore .htaccess and use server blocks instead.

Will the .com rank better than the .org?

Not because of the extension. Google gives neither an advantage. Choose for brand and audience, then migrate carefully.

The bottom line

A .org to .com switch is a technical project, not an address change. Map every URL, redirect page to page, keep the content steady, align canonicals and sitemaps, tell Google, and keep the old domain running. Then watch the data closely for three months. If you have a client move coming up, send SoftVolt AI a brief or see our technical SEO services.