> For the complete documentation index, see [llms.txt](https://support.agentfire.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.agentfire.com/launch/redirects-and-dns-management/articles-1505032-preserving-seo-rankings-from-your-old-website-301-redirects.md).

# How to Keep Your Google Rankings When You Move Your Website

What to do before and after moving your website to AgentFire so Google and visitors still find your old pages.

When you move to AgentFire, your domain stays the same, but some page addresses usually change. For example, `yourdomain.com/miami_page2930209.html` might become `yourdomain.com/miami-homes/`. Anyone following an old link, from Google or anywhere else, then lands on a "page not found" page, unless you add a **301 redirect** from the old address to the new one.

Redirects help Google carry your old pages' standing over to the new ones. Rankings often move around for a few weeks after any move.

## Before your old website goes away

Make a list of your old site's page addresses, especially the ones people visit most. You can usually get them from your old site's sitemap (often `yourdomain.com/sitemap.xml`), your Google Search Console or Analytics. Once the old site is gone, the list is much harder to rebuild, and we don't get a copy of it. If you can, match each old address to its new page now too, so the redirects can go in as soon as you launch.

## After you launch

{% stepper %}
{% step %}

### Match old pages to new ones

For each old address that changed, pick the closest new page. Pages whose address is the same on both sites don't need anything.
{% endstep %}

{% step %}

### Add the redirects

Add a **301** redirect for each one in Redirect Manager. See [How to Add a 301 (Permanent) Redirect](/launch/redirects-and-dns-management/articles-1505040-how-to-do-301-redirects.md). For a long list, email <support@agentfire.com> with your old and new addresses.
{% endstep %}

{% step %}

### Test, then check Search Console

Right after launch, open a few old addresses in a private window to check they land on the right pages. A few weeks later, check your Search Console page indexing report for "Not found (404)" pages, and add redirects for any that matter. See [How to Set Up Google Search Console](/launch/google-services/articles-1504905-01-setting-up-google-search-console.md).
{% endstep %}
{% endstepper %}

## Common Questions

<details>

<summary>My old site is already gone. Is it too late?</summary>

No. Check Search Console for pages Google can't find anymore, and redirect the ones that have a matching new page.

</details>

<details>

<summary>I have another domain that isn't my AgentFire website. How do I send it here?</summary>

Redirect Manager only works for your AgentFire website's domain. For another domain, set up a forward where it's registered. See [How to Forward Extra Domains to Your Website](/launch/i-have-more-domains-i-want-to-forward-to-agentfire-website-is-it-possible.md).

</details>

<details>

<summary>Should I redirect every old page to my home page?</summary>

No. Redirect each one to its closest matching page. Old pages with no match can stay "not found".

</details>

<details>

<summary>Do I need Google's Change of Address tool?</summary>

Only if your domain changes too. Moving your website to AgentFire on the same domain doesn't need it.

</details>