Preserving SEO and redirects

When you leave WordPress, URL shapes often change—for example /2020/05/my-landscape-shot/ may become /blog/my-landscape-shot on ArtInStack. Search engines and inbound links still hit the old paths unless you redirect them.

How redirects work on ArtInStack

During import, the migration job writes a redirect map: each legacy source path (from your WordPress export) maps to the new target path on your ArtInStack site. These rules are stored for your workspace and enforced when visitors request your public site.

Behavior	Detail
Redirect type	301 Permanent by default — tells search engines the move is permanent
Where it runs	On your live site hostname (workspace subdomain or custom domain) before the page renders
Performance	Rules are cached briefly (~60 seconds) so repeat visitors are not slowed down
Trailing slashes	Both /my-post and /my-post/ are matched — enter paths once in reports; the platform normalizes
Case	Source paths are compared case-insensitively
Loop safety	Rules where source equals target are rejected automatically

Redirects apply to path only — you do not include https:// or your domain in the stored source path.

Reviewing redirects after import

There is no separate “URL routing” screen in the dashboard today. Redirects created by migration are applied automatically.

To audit them:

1. Go to Settings → Import Site → Reports.
2. Open a completed job and download the JSON report.
3. Find the redirectMap section — each entry lists fromPath, toPath, and status code.

Use this list when validating Search Console coverage or sharing with your SEO consultant before DNS cutover.

Re-running an import for the same source path updates the existing redirect rather than duplicating it.

URL changes to expect

Legacy (WordPress)	Typical ArtInStack route
Dated blog permalink /2020/03/title/	/blog/title
Root-level page /about/	/about
Portfolio CPT /portfolio/project-name/	/portfolio/project-name or linked collection URL

Blog posts always live under /blog/{slug} on ArtInStack unless you add further redirects manually (future dashboard tools) or adjust navigation.

Prerequisites for a safe cutover

• Imported pages are published and preview correctly on your workspace URL.
• Migration report shows acceptable asset and content counts.
• Redirect report covers your highest-traffic legacy URLs (top blog posts, portfolio landing pages, press links).
• Custom domain is verified under Settings → General when you are ready to switch DNS.

Implementation steps (cutover day)

1. Lower DNS TTL a day ahead at your registrar (optional but helps faster rollback).
2. Publish all imported pages and posts you want live on day one.
3. Spot-check five to ten old URLs in a private browser — each should 301 to the new location.
4. Point DNS to ArtInStack per Set up your workspace.
5. Re-test the same legacy URLs on your custom domain.
6. In Google Search Console (if you use it), submit your sitemap and monitor Coverage for a few weeks.

Verifying your setup

• Visiting an old WordPress path on your live hostname returns 301 to the new page (not 404).
• New pages load on the expected /blog/… or /about routes.
• Migration report redirectMap includes entries for your priority URLs.
• No redirect chains longer than a single hop for paths you tested.

Troubleshooting and common pitfalls

Symptom	Likely cause	What to do
404 on old URL	Path not in export or redirect skipped	Confirm slug existed in WXR; check report for that fromPath
404 only on custom domain	DNS or SSL not finished	Wait for domain verification; test workspace URL first
Images broken but page loads	Asset fetch failed during import	Re-run media after fixing public URL; see After your import
Duplicate content in search	Old WordPress still live on same domain	Take legacy site offline or noindex it after cutover