Will rankings and AI citations drop after a domain or URL change?
Done right, a 301 does not cost you rankings, but a move takes time. Google's site move documentation says permanent redirects (301, 308) do not lose PageRank, and that for a small or medium site most pages take "a few weeks" to move. How AI engines treat a 301 is not covered: the OpenAI and Perplexity crawler documentation say nothing about redirects or site moves, so we could not verify it. The safe route is to follow Google's process and then check by asking AI yourself.
| Question | Is there an official statement? | Our conclusion |
|---|---|---|
| Does a 301 lose rankings? | Google site move documentation (checked 2026-11-07): permanent redirects do not lose PageRank | Done right, you do not lose rankings because of the 301 itself |
| How long does a move take? | Google: for a small or medium site, most pages take "a few weeks"; larger sites take longer | Expect traffic to fall on the old URLs and rise on the new ones during this time |
| Do AI crawlers follow a 301? | Neither the OpenAI nor the Perplexity crawler documentation mentions redirects (checked 2026-11-07) | Not verified. Make sure old URLs return a 301 with curl, then spot-check by asking AI |
| Old links already inside AI answers | No official statement | No data. Keep the old URLs on 301 and wait for them to be re-crawled |
Which changes count as a "site move" and need Search Console's Change of Address tool?
Only a change of domain or subdomain needs the Change of Address tool. Google's move documentation (checked 2026-11-07) says it is only for moving from one domain or subdomain to another; every other change needs 301s plus a new sitemap.
| Change | Need the Change of Address tool? | What to do |
|---|---|---|
| example-old.com becomes example-new.com | Yes | 301s, Change of Address, new sitemap, update internal and external links |
| www.example.com moves to example.com (same domain) | Don't | 301s, and change the canonical to the new form |
| http becomes https | Don't | 301s; Google detects it on its own |
| Changing paths on the same domain, for example /guide/a to /a | Don't | 301 each old path to its new path, update the sitemap and internal links |
| Change of host or CDN, same URLs | Don't | Check that robots.txt and the TLS certificate are still in place in the new environment |
How do you do a 301 without losing signals?
Send each old URL one-to-one to its matching new URL in a single step. Google's requirements: prefer server-side permanent redirects (301 or 308); send each old URL straight to the final URL, ideally no more than 3 hops and fewer than 5; do not point many old URLs at the home page or an unrelated page.
One-to-one, keep path and parameters
/r/abc?lang=zh should go to /r/abc?lang=zh on the new domain, not to the home page.
No chains
If old URL A goes to B and then to C, change it so A goes straight to C.
301 for pages, endpoints as needed
Page requests (GET and HEAD) get a 301; POST requests such as webhooks may not follow a redirect, so keep serving them on the old address. The kagentx example below does exactly that.
How do you use Search Console's Change of Address tool?
Move first, set up the 301s first, and submit last. The Search Console help page (checked 2026-11-07) says you must own both the old and the new domain-level properties with the same Google account; before submitting, 301 the old home page to the new one; submit every verified variant of the old domain (www, non-www and so on). After you submit, signals are forwarded for 180 days, Google prefers the new site's canonical URLs for 180 days, and you can cancel the request within 180 days.
| Item | What the documentation says | Note |
|---|---|---|
| Who can use it | The owner of both the old and the new domain-level property, with the same account | Path-level properties (such as example.com/shop/) do not work |
| Before submitting | The old home page already 301s to the new home page | Ideally all canonical URLs are already redirected |
| How long it takes effect after submitting | Signals are forwarded and the new site is preferred for 180 days | Can be cancelled within 180 days |
| How long to keep redirects | The Change of Address page says at least 180 days; the site move page says generally at least 1 year | Keep them longer if the old URLs still get search traffic |
A year is the minimum for redirects: letting the old domain expire turns every old link into a dead link. MochiStamp's approach is in the table below.
What do you do about the sitemap, canonicals and old links?
Submit a sitemap that lists only the new URLs, change canonicals and hreflang to the new URLs, and write internal links with the new address instead of relying on redirects. Ask other sites to update their links; the ones that do not will be kept by the 301. For hreflang on multilingual sites see How do multilingual sites get cited by AI search?, for how to write lastmod see Does sitemap lastmod matter to AI crawlers?, to tell search engines quickly after the change you can use What is IndexNow?, and for how to watch a move in Search Console see How do you use Search Console on a new site?.
Do not forget robots.txt: if the new environment still carries a development-time noindex or a crawler block, none of the new URLs can be read after the move. The rules are in How to write robots.txt for AI crawlers.
Have we moved URLs ourselves? What did we do and what is the state now?
Four times. The "Now" column is what curl returned on 2026-11-07; the "What we did" column comes from the decision records in our repositories. We have no before-and-after search or AI citation data for these moves, so we describe what we did and make no claim about the effect.
| Who | Date | Approach | Now (curl, 2026-11-07) |
|---|---|---|---|
| MochiStamp domain change | 2026-10-14 | mochistamp.com is the main domain; srakb.com and both www hosts 301 to the same path; srakb.com is renewed for at least another year so the redirects keep working | srakb.com/en/ returns a 301 to mochistamp.com/en/; www.srakb.com/ returns a 301 to mochistamp.com/ |
| MochiStamp merging old pages | 2026-10-30 | One URL per group of search terms: animated stickers keep only /animated-stickers, the old tutorial's content was merged in, and its old addresses in four languages 301 to it | mochistamp.com/guide/ugoku-stamp returns a 301 to /animated-stickers |
| kagentx redesign (same domain) | 2026-10-28 | The home page changed from the AI Agent library to the marketing site; the library moved to /agents/, product pages at /p/… kept their addresses; old /#p=… links go to /agents/#p=…; the brand text changed from AgentHub to kagentx | kagentx.com/agents/ returns 200 |
| kagentx app moves to a new subdomain | 2026-10-28 | The growth service moved from app.kagentx.com to growth.kagentx.com; page requests (GET, HEAD) get a 301 to the same path and parameters on the new address; the payment callback (POST) is not redirected and is still served on the old address | app.kagentx.com/r/abc?lang=zh returns a 301 to growth.kagentx.com/r/abc?lang=zh |
For MochiStamp's merge, see MochiStamp's animated stickers page: one URL per topic so signals are not split. For how to write update dates, see Does content freshness matter for AI search?.
One more detail: the URL registered with MochiStamp's payment provider is staying on the old domain for now (changing it triggers a compliance review and a 30-day lock). When you change domain, list the URLs registered with third-party services separately; do not expect redirects to change them for you.
What do you do on the day of the move and after it, step by step?
1. List every old URL
Sources: the sitemap, GA4's pages report, server logs, and Search Console's links report. Images, scripts and PDFs count too.
2. Write an "old URL → new URL" mapping table
One row per old URL; content you are not moving should clearly return 404 or 410, not all point to the home page.
3. Check the new environment first
robots.txt does not block crawlers, no development-time noindex is left, the TLS certificate is valid, and the server can take the extra crawling during the move.
4. Turn on the 301s and verify each with curl
The commands below check three things at once: the status code, the Location, and whether the new URL answers 200 directly.
# 逐个旧网址看:状态码应是 301,Location 应是对应的新网址 curl -sI https://old.example.com/en/ | grep -iE "^HTTP|^location" # 带参数的页面也要保持路径和参数 curl -sI "https://old.example.com/r/abc?lang=zh" | grep -iE "^HTTP|^location" # 新网址应直接返回 200,不再跳转 curl -sI https://new.example.com/en/ | grep -iE "^HTTP"
5. Change canonicals, hreflang and internal links
Write the new URLs everywhere; the sitemap lists only new URLs and is submitted to Search Console.
6. If you changed domain, submit Change of Address
Submit after the 301s and the new sitemap are in place, for every variant of the old domain.
7. Check once a week for a month
Look at Search Console's indexing coverage and search performance, and at server logs for unexpected 404s, then ask AI a few questions the way How do you measure AI visibility? Four metrics and a table you can follow describes and see whether it cites the new or the old URL.
Which status code to use when unifying trailing slashes during a migration, and how to self-check: see Is a 307 on trailing slashes bad for SEO? How to choose between 301, 302, 307 and 308.
FAQ
Will my Google rankings drop after a domain change?
Google's site move documentation (checked 2026-11-07) says 301 and other permanent redirects do not lose PageRank, but for a small or medium site most pages take a few weeks to move, and it is normal for traffic to fall on the old URLs and rise on the new ones meanwhile.
When is the Change of Address tool required?
Only when moving from one domain or subdomain to another. http to https, www to non-www and back, or changing paths on the same domain do not need it (Google move documentation, checked 2026-11-07).
How long should 301 redirects stay?
Google's move documentation says generally at least 1 year, the Change of Address help page says at least 180 days, and keep them longer if the old URLs still get search traffic. MochiStamp treats its old domain srakb.com as "renew for at least another year".
Does AI search follow a 301?
There is no official statement. The OpenAI and Perplexity crawler documentation (checked 2026-11-07) mention neither redirects nor site moves, so we could not verify it. What to do: make sure old URLs return a 301, then ask AI yourself and check which URL it cites.
Should webhooks be redirected when URLs change?
No. Page requests get a 301, but POST requests such as webhooks may not follow a redirect, so kagentx 301s the pages on app.kagentx.com to growth.kagentx.com and keeps serving the payment callback on the old address.
Sources
- Google Search Central · Site moves with URL changes (checked 2026-11-07)
- Search Console Help · Change of Address tool (checked 2026-11-07)
- OpenAI · Overview of OpenAI Crawlers (Viewed 2026-11-07; it does not mention redirects)
- Perplexity · Perplexity Crawlers (Viewed 2026-11-07; it does not mention redirects)
- MochiStamp · srakb.com、/guide/ugoku-stamp 的 301 实测 (Tested with curl on 2026-11-07; what we did comes from the repository decision records)
- kagentx · app.kagentx.com 的 301 实测 (Tested with curl on 2026-11-07; what we did comes from the repository decision records)
- kagentx evaluations: the data on the case study pages; each example gives its date.