{"id":80,"date":"2026-09-21T21:13:18","date_gmt":"2026-09-21T21:13:18","guid":{"rendered":"https:\/\/austins.website\/blog\/domain-change-seo\/"},"modified":"2026-09-29T17:13:53","modified_gmt":"2026-09-29T17:13:53","slug":"domain-change-seo","status":"publish","type":"post","link":"https:\/\/austins.website\/blog\/domain-change-seo\/","title":{"rendered":"Domain Change SEO: What Happens to Your Rankings When You Rebrand"},"content":{"rendered":"<p>Changing your domain name is one of those projects that sounds simple until <a href=\"https:\/\/austins.website\/consulting\/migrations\/\">website migration SEO<\/a> gets invited to the meeting.<\/p>\n<p>Buy the new domain. Point the website at it. Update the logo. Done.<\/p>\n<p>Except your old domain may have years of search history attached to it. Other websites link to its URLs. Google has crawled and indexed its pages. Your internal links reinforce its site structure. Customers recognize the hostname in search results. Analytics platforms, tracking systems, XML sitemaps, canonical tags, and dozens of other systems may reference it.<\/p>\n<p>A domain change asks search engines to understand that all of those signals now belong somewhere else.<\/p>\n<p>That does not mean changing domain names automatically destroys your rankings. A properly planned domain migration can preserve the SEO value you have already earned. A sloppy one can turn a rebrand into a very expensive technical SEO project.<\/p>\n<p>Here is what actually happens when you change domains, where rankings can go wrong, and how to make the move without giving Google an identity crisis.<\/p>\n<h2>What Happens to SEO When You Change Your Domain?<\/h2>\n<p>A domain change replaces the hostname used by your existing URLs.<\/p>\n<p>If a company moves from <strong>oldbrand.com\/services<\/strong> to <strong>newbrand.com\/services<\/strong>, the content may be identical, but the URL Google knows has changed.<\/p>\n<p>That distinction matters.<\/p>\n<p>Search engines have already collected signals about the old URLs. Those signals can include backlinks, internal links, canonical relationships, content history, and other information used to crawl, index, and evaluate pages.<\/p>\n<p>During a <a href=\"https:\/\/austins.website\/blog\/domain-migration-seo\/\">domain migration<\/a>, you need to give the search engine enough consistent signals to connect the old URLs with their replacements.<\/p>\n<p>Google&#8217;s <a href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/site-move-with-url-changes\" target=\"_blank\" rel=\"noopener\">Site Moves and Migrations guidance<\/a> from Google Search Central specifically treats a domain name change as a site move involving URL changes. Its recommended process includes preparing the new site, creating a URL map, implementing server-side redirects, and notifying Google about the domain move through Google Search Console.<\/p>\n<p>The important word here is <strong>move<\/strong>.<\/p>\n<p>You do not want search engines interpreting the new domain as an unrelated website that happens to contain similar content. You want them to understand that the existing site moved to a new address.<\/p>\n<h2>Will Changing Your Domain Name Hurt Your Rankings?<\/h2>\n<p>It can.<\/p>\n<p>A domain migration introduces temporary uncertainty because search engines have to recrawl old URLs, discover their redirects, crawl the new URLs, process those relationships, and update their indexes.<\/p>\n<p>That creates opportunities for rankings and organic traffic to fluctuate.<\/p>\n<p>But the domain name change itself is not necessarily the problem.<\/p>\n<p>Most severe migration losses come from everything that changes around it.<\/p>\n<p>For example, imagine a company combines a rebranding project with:<\/p>\n<ul>\n<li>\n<p>A new domain name<\/p>\n<\/li>\n<li>\n<p>A website redesign<\/p>\n<\/li>\n<li>\n<p>A new CMS<\/p>\n<\/li>\n<li>\n<p>Different URL structures<\/p>\n<\/li>\n<li>\n<p>Rewritten content<\/p>\n<\/li>\n<li>\n<p>New navigation<\/p>\n<\/li>\n<li>\n<p>Deleted pages<\/p>\n<\/li>\n<li>\n<p>Changed internal links<\/p>\n<\/li>\n<\/ul>\n<p>Now you are not testing one variable.<\/p>\n<p>You are changing half the website.<\/p>\n<p>If search engine rankings fall afterward, identifying the cause becomes much harder. Was link equity lost through broken redirects? Did important content disappear? Did internal links change? Did a new template accidentally introduce a <strong>noindex<\/strong> directive? Did Googlebot discover thousands of unnecessary URLs in the new CMS?<\/p>\n<p>This is why I prefer isolating changes when the project allows it.<\/p>\n<p>If the business must change the brand, domain, CMS, design, content, and architecture simultaneously, the migration needs significantly more QA.<\/p>\n<h2>Why Rankings Can Drop During a Domain Migration<\/h2>\n<p>The biggest SEO problems during a domain change are usually technical rather than mysterious.<\/p>\n<h3>Missing or Incorrect 301 Redirects<\/h3>\n<p>Every valuable URL on the old domain should have a planned destination.<\/p>\n<p>For most equivalent pages, that means a server-side permanent redirect from the old URL directly to the corresponding URL on the new domain.<\/p>\n<p>For example:<\/p>\n<p><strong>oldbrand.com\/commercial-roofing<\/strong> -> <strong>newbrand.com\/commercial-roofing<\/strong><\/p>\n<p>A common mistake is redirecting every old URL to the new homepage.<\/p>\n<p>That may be convenient for whoever writes the redirect rules, but it throws away information about which old page corresponds to which new page.<\/p>\n<p>Your <a href=\"https:\/\/austins.website\/blog\/301-redirect-mapping\/\">redirect map<\/a> should preserve those relationships whenever an equivalent destination exists.<\/p>\n<h3>Redirect Chains<\/h3>\n<p>A redirect should ideally take users and crawlers directly from the old URL to its final destination.<\/p>\n<p>You do not want:<\/p>\n<p>Old URL -> intermediate URL -> another URL -> new URL<\/p>\n<p>Those redirect chains create unnecessary crawl steps and complicate troubleshooting.<\/p>\n<p>This is particularly important if the old site already has years of redirects sitting in its configuration. Audit existing redirects before launch and collapse chains wherever practical.<\/p>\n<h3>Important Pages Disappear<\/h3>\n<p>Rebranding often becomes spring cleaning.<\/p>\n<p>Someone notices 400 old pages and decides the new website would look much cleaner with 75.<\/p>\n<p>Maybe it would.<\/p>\n<p>But deleting pages without looking at their SEO value first is a good way to discover that the ugly 2018 service page you hated had 43 backlinks and generated 12% of your organic leads.<\/p>\n<p>Before deciding what survives the migration, inventory existing pages using data from Google Search Console, Google Analytics, backlink tools, and a site crawl.<\/p>\n<p>Tools such as Screaming Frog, Ahrefs, Semrush, and Moz can help identify URLs that deserve additional attention.<\/p>\n<p>The decision to remove a page should be based on evidence, not whether it fits the new navigation.<\/p>\n<h3>Internal Links Still Point to the Old Domain<\/h3>\n<p>301 redirects are a safety net, not your new internal linking strategy.<\/p>\n<p>After the domain change, internal links should point directly to URLs on the new domain.<\/p>\n<p>If every navigation link, contextual link, image reference, or canonical URL still points to the old domain, Googlebot has to repeatedly encounter redirects while crawling your own website.<\/p>\n<p>Update internal links at the source.<\/p>\n<h3>Canonical Tags Are Wrong<\/h3>\n<p>Canonical tags are another place where migrations get weird fast.<\/p>\n<p>The pages on the new domain should generally reference the intended canonical URLs on the new domain. If the migration launches while canonical tags still reference the old hostname, you are sending conflicting signals.<\/p>\n<p>Your redirects say, &#8220;We moved.&#8221;<\/p>\n<p>Your canonical tags say, &#8220;Actually, the old address is still preferred.&#8221;<\/p>\n<p>Do not make a search engine referee an argument between your own technical signals.<\/p>\n<h2>Domain Change SEO Starts Before Launch<\/h2>\n<p>The safest domain migration begins before anyone changes DNS records.<\/p>\n<p>You need a baseline.<\/p>\n<p>At minimum, capture:<\/p>\n<ul>\n<li>\n<p>Current indexed pages<\/p>\n<\/li>\n<li>\n<p>Organic landing-page traffic<\/p>\n<\/li>\n<li>\n<p>Search queries and clicks<\/p>\n<\/li>\n<li>\n<p>Search engine rankings<\/p>\n<\/li>\n<li>\n<p>\nBacklinks to important URLs<\/p>\n<\/li>\n<li>\n<p>Existing redirects<\/p>\n<\/li>\n<li>\n<p>Current XML sitemaps<\/p>\n<\/li>\n<li>\n<p>Canonical tags<\/p>\n<\/li>\n<li>\n<p>Robots directives<\/p>\n<\/li>\n<li>\n<p>Conversion performance<\/p>\n<\/li>\n<\/ul>\n<p>I typically start with a full crawl in Screaming Frog and exports from GSC, Google Analytics, Ahrefs or Semrush, and whatever ranking system is being used.<\/p>\n<p>That gives you a record of the site search engines understand today.<\/p>\n<p>It also creates something teams routinely forget during migrations: a definition of success.<\/p>\n<p>Without a baseline, &#8220;traffic looks lower&#8221; becomes the entire post-launch analysis.<\/p>\n<p>With one, you can compare individual pages, query groups, rankings, indexed pages, clicks, conversions, and organic traffic against pre-migration performance.<\/p>\n<h2>Build a URL Map Before You Build Redirects<\/h2>\n<p>The URL map is one of the most important documents in a domain migration.<\/p>\n<p>Take every relevant URL on the old hostname and assign it a destination.<\/p>\n<p>For pages that remain unchanged except for the domain name, the mapping is easy:<\/p>\n<p><strong>oldbrand.com\/page-a<\/strong> -> <strong>newbrand.com\/page-a<\/strong><\/p>\n<p>If the site structure changes, it becomes more complicated:<\/p>\n<p><strong>oldbrand.com\/services\/old-service-name<\/strong> -> <strong>newbrand.com\/solutions\/new-service-name<\/strong><\/p>\n<p>Do not rely exclusively on a wildcard rule unless the old and new URL structures truly match.<\/p>\n<p>Prioritize URLs with organic traffic, backlinks, conversions, rankings, and meaningful business value.<\/p>\n<p>That is how you protect link equity rather than hoping the redirect configuration happens to catch everything.<\/p>\n<h2>Use 301 Redirects for the Domain Change<\/h2>\n<p>For a permanent domain move, use permanent server-side redirects.<\/p>\n<p>Google&#8217;s site-move documentation recommends setting up redirects from old URLs to the appropriate new URLs as part of a site move.<\/p>\n<p>Your 301 redirects accomplish two things at once.<\/p>\n<p>First, people following old links reach the correct page.<\/p>\n<p>Second, search engines receive an explicit signal that the resource has permanently moved.<\/p>\n<p>The best implementation is usually one hop:<\/p>\n<p>Old URL -> final new URL<\/p>\n<p>After launch, crawl the old URL list and verify the status code and final destination for each one.<\/p>\n<p>Do not assume the redirect rules worked because the homepage loaded correctly on your phone.<\/p>\n<p>Test them.<\/p>\n<h2>Update Google Search Console<\/h2>\n<p>A domain change also requires work inside Google Search Console.<\/p>\n<p>Verify both the old and new properties before migration day. You do not want to discover during launch that the person with access left the company six months ago.<\/p>\n<p>Google provides a Change of Address tool specifically for moving a site from one domain or subdomain to another. Google says the tool should be used after the site has been moved and redirects are in place.<\/p>\n<p>There is an important detail here for domain name changes.<\/p>\n<p>Google&#8217;s current documentation says that when moving domains, you should submit Change of Address requests for the relevant verified variants of the old domain, including applicable subdomains and www\/non-www variants. The tool affects paths under the property you submit but does not automatically move subdomains beneath it.<\/p>\n<p>That makes property verification something to plan before launch, not improvise afterward.<\/p>\n<p>The Change of Address tool is not a replacement for redirects.<\/p>\n<p>It complements them.<\/p>\n<p>Google explicitly says to move and redirect the site first, then use the tool.<\/p>\n<h2>Submit New XML Sitemaps<\/h2>\n<p>Create XML sitemaps containing the canonical URLs from the new domain and submit them through GSC.<\/p>\n<p>Then watch what happens.<\/p>\n<p>You want Google to discover the new URLs, recrawl them, and gradually replace the old indexed pages with their new equivalents.<\/p>\n<p>The URL Inspection tool in Search Console can show index information for individual URLs and lets site owners request indexing when appropriate.<\/p>\n<p>Do not spend launch day manually requesting indexing for 10,000 pages.<\/p>\n<p>For a normal site migration, your redirects, internal links, XML sitemaps, and crawlable architecture should do most of that work at scale.<\/p>\n<h2>Check Robots.txt and Indexing Directives<\/h2>\n<p>Staging environments are commonly blocked from search engines.<\/p>\n<p>That is usually good.<\/p>\n<p>Shipping the staging restrictions to production is less good.<\/p>\n<p>Before launch, verify that the new domain&#8217;s <strong>robots.txt<\/strong>, robots meta directives, and other crawl or index controls allow search engines to access the pages you expect to rank.<\/p>\n<p>This is a five-minute check capable of preventing a five-alarm SEO meeting.<\/p>\n<p>Also verify that canonical tags, hreflang where applicable, structured data URLs, image URLs, and other hostname-dependent references use the correct domain.<\/p>\n<h2>Update DNS Records Carefully<\/h2>\n<p>The SEO team may not own DNS records, but DNS is part of the launch.<\/p>\n<p>Confirm the new hostname resolves correctly, HTTPS works, certificates are valid, and both expected hostname variants behave properly.<\/p>\n<p>The old domain must continue resolving so its permanent redirects can function.<\/p>\n<p>If you shut the old hostname down, those backlinks cannot magically find the new one.<\/p>\n<p>The redirect infrastructure needs to remain available long after launch.<\/p>\n<h2>What About Your Backlinks?<\/h2>\n<p>You do not need to manually change every backlink on the internet.<\/p>\n<p>That would be a fun email campaign if your definition of fun is emailing 1,700 webmasters about URLs from 2019.<\/p>\n<p>Correct 301 redirects allow old links to resolve to their new destinations and help search engines understand the move.<\/p>\n<p>Still, I recommend manually updating the highest-value links when you can.<\/p>\n<p>Start with links you control:<\/p>\n<ul>\n<li>\n<p>Company profiles<\/p>\n<\/li>\n<li>\n<p>Major directory listings<\/p>\n<\/li>\n<li>\n<p>Partner websites<\/p>\n<\/li>\n<li>\n<p>Social profiles<\/p>\n<\/li>\n<li>\n<p>Important citations<\/p>\n<\/li>\n<li>\n<p>Paid placements you manage<\/p>\n<\/li>\n<li>\n<p>Other company-owned websites<\/p>\n<\/li>\n<\/ul>\n<p>Then consider outreach for particularly authoritative external backlinks.<\/p>\n<p>The goal is not to replace every historical link. It is to make the strongest signals as direct and consistent as reasonably possible.<\/p>\n<h2>Don&#8217;t Forget Bing<\/h2>\n<p>Google gets most of the attention in SEO migration plans, but it is not the only search engine crawling your site.<\/p>\n<p>Add and verify the new domain in Bing Webmaster Tools as well. Bing supports adding sites manually or importing verified sites from Google Search Console.<\/p>\n<p>Bing&#8217;s URL Inspection tool can also report crawl, index, SEO, and markup information for URLs on a verified domain.<\/p>\n<p>Treat Bing verification and monitoring as part of the <a href=\"https:\/\/austins.website\/blog\/seo-migration-checklist\/\">migration checklist<\/a> rather than an afterthought.<\/p>\n<h2>How Long Does a Domain Migration Take?<\/h2>\n<p>There is no universal recovery date.<\/p>\n<p>Any agency promising that every domain migration will fully settle in an exact number of days is giving you more certainty than the underlying systems support.<\/p>\n<p>The timeline depends on factors such as site size, crawl frequency, internal architecture, redirect implementation, backlink profile, and how much else changed during the migration.<\/p>\n<p>Search engines need time to recrawl old URLs, process permanent redirects, discover the new URLs, and reindex them.<\/p>\n<p>Your job is not to stare at the homepage ranking every morning until everyone gets nervous.<\/p>\n<p>Monitor the migration systematically.<\/p>\n<p>Track indexed pages, crawl errors, rankings, clicks, impressions, click-through rates, organic landing-page traffic, and conversions. Compare them against your pre-launch benchmark.<\/p>\n<p>A temporary fluctuation and a broken migration are different problems.<\/p>\n<p>The data tells you which one you have.<\/p>\n<h2>How to Monitor SEO After Changing Domains<\/h2>\n<p>For the first several weeks after launch, monitoring should be more aggressive than your normal SEO reporting cadence.<\/p>\n<p>Watch GSC for crawl errors and indexing changes. Check how Googlebot is discovering the new URLs. Crawl both domains to verify that permanent redirects remain intact.<\/p>\n<p>Compare rankings at the page and query level rather than looking only at a sitewide average.<\/p>\n<p>Check organic traffic in Google Analytics, but do not stop there. Traffic can hide problems.<\/p>\n<p>If informational traffic rises while high-converting service pages disappear from search results, the sitewide number can look perfectly respectable while revenue gets punched in the face.<\/p>\n<p>Segment the pages that mattered before the migration and monitor those specifically.<\/p>\n<h2>Domain Migration vs. Website Redesign<\/h2>\n<p>A domain migration and <a href=\"https:\/\/austins.website\/blog\/website-redesign-seo\/\">website redesign<\/a> are not the same project, even though companies frequently combine them.<\/p>\n<p>Changing the domain changes URLs.<\/p>\n<p>A website redesign may change templates, content, navigation, page layouts, structured data, performance, internal links, and sometimes the entire URL architecture.<\/p>\n<p>Combining them increases the number of variables involved.<\/p>\n<p>When possible, preserve important URLs, content, metadata, and architecture during the domain move. Let the search engine process the change of address before making another round of major SEO changes.<\/p>\n<p>When that is not practical, your pre-launch crawl, URL mapping, staging QA, and post-launch monitoring become much more important.<\/p>\n<h2>Rebranding Adds Another Layer<\/h2>\n<p>A rebranding project is usually more complicated than swapping one domain name for another.<\/p>\n<p>The company name may change across the website, title tags, structured data, social profiles, local listings, citations, backlinks, and other external references.<\/p>\n<p>For local businesses, a rebrand may also require coordinated updates to business listings and other <a href=\"https:\/\/austins.website\/consulting\/local-seo\/\"><br \/>\nlocal SEO<\/a> signals.<\/p>\n<p>The technical migration still matters, but so does consistency.<\/p>\n<p>The new brand, domain, and business identity should tell the same story everywhere search engines and customers encounter them.<\/p>\n<p>That is why rebranding should not be treated as a design project with &#8220;SEO redirects&#8221; added to the launch checklist three days before production.<\/p>\n<p>SEO needs a seat at the table while the migration is being planned.<\/p>\n<h2>When Should You Change Domains?<\/h2>\n<p>A domain migration should solve a real business problem.<\/p>\n<p>Rebranding is an obvious example. A merger, acquisition, domain consolidation, or move away from a genuinely problematic legacy domain can also justify it.<\/p>\n<p>What I would not do is change a healthy domain because someone thinks a different keyword in the domain name might provide an SEO shortcut.<\/p>\n<p>A domain with years of backlinks, brand recognition, indexed pages, and search performance is an asset.<\/p>\n<p>Moving it creates work and risk.<\/p>\n<p>Sometimes that risk is absolutely worth taking. Just make sure the reason comes from the business strategy rather than an imagined ranking hack. The same principle applies when a <a href=\"https:\/\/pointsourcemarketing.com\/\">performance marketing agency<\/a> is coordinating SEO with broader acquisition and growth initiatives.<\/p>\n<h2>The Domain Change SEO Checklist<\/h2>\n<p>Before launch, benchmark rankings, organic traffic, indexed pages, backlinks, and conversions. Crawl the old website. Build a complete URL inventory and map important old URLs to appropriate destinations. Configure and test 301 redirects. Update internal links, canonical tags, structured data, XML sitemaps, analytics, and hostname references. Verify the old and new properties in Google Search Console and add the new site to Bing Webmaster Tools.<\/p>\n<p>At launch, verify DNS and HTTPS, remove unintended staging restrictions, confirm that <strong>robots.txt<\/strong> allows the right crawling, test permanent redirects, submit the new XML sitemaps, and use Google&#8217;s Change of Address tool when applicable.<\/p>\n<p>After launch, recrawl both domains. Monitor GSC for crawl errors and indexing changes. Compare organic traffic, search engine rankings, and conversions against your benchmark. Check priority backlinks and update the most valuable ones where practical.<\/p>\n<p>Then keep monitoring.<\/p>\n<p>A migration is not finished because somebody posted the new logo on LinkedIn.<\/p>\n<p>It is finished when search engines and users have successfully made the move too.<\/p>\n<h2>FAQ<\/h2>\n<h3>What does &#8220;domain change&#8221; mean?<\/h3>\n<p>A domain change means moving a website from one domain name or hostname to another. For SEO, this changes the URLs search engines have previously crawled and indexed, so the old URLs need to be mapped and redirected to their appropriate replacements.<\/p>\n<h3>Does changing your domain name affect SEO?<\/h3>\n<p>Yes. Changing your domain name can affect SEO because search engines must process the relationship between the old and new URLs. Correct URL mapping, 301 redirects, internal links, XML sitemaps, and Search Console configuration help search engines understand that the website has moved rather than disappeared.<\/p>\n<h3>Will I lose my search rankings during a domain change?<\/h3>\n<p>A domain change can cause ranking fluctuations, but a major sustained loss is not something you should simply accept as inevitable. Migration problems such as missing redirects, deleted content, incorrect canonical tags, blocked crawling, or major simultaneous site changes can contribute to ranking losses.<\/p>\n<h3>How long does it take to recover SEO after a domain change?<\/h3>\n<p>There is no fixed recovery period that applies to every site. Search engines need to recrawl the old URLs, process redirects, crawl the new URLs, and update their indexes. Site size, crawl activity, redirects, backlinks, and the scope of other changes can all affect the timeline.<\/p>\n<h3>Do I need to update all my backlinks manually?<\/h3>\n<p>No. Proper permanent redirects allow people and search engines following backlinks to old URLs to reach their new destinations. It is still worth updating important backlinks you control and, where practical, asking high-value external sites to link directly to the new URLs.<\/p>\n<h3>How can I maintain my SEO rankings during a domain change?<\/h3>\n<p>Benchmark performance before the move, map old URLs to appropriate new URLs, implement direct 301 redirects, preserve valuable content, update internal links and canonical tags, submit new XML sitemaps, use the Change of Address tool where appropriate, and monitor crawling, indexing, rankings, organic traffic, and conversions after launch.<\/p>\n<h3>When should you do a domain migration?<\/h3>\n<p>A domain migration makes sense when there is a legitimate business reason, such as rebranding, merging websites, consolidating domains, or replacing a legacy domain that no longer fits the company. It generally should not be done solely because a different domain name looks more SEO-friendly.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Changing domains during a rebrand? Learn how domain change SEO works and how to protect rankings, backlinks, and organic traffic during migration.<\/p>\n","protected":false},"author":0,"featured_media":81,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"pagelayer_contact_templates":[],"_pagelayer_content":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-80","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/austins.website\/blog\/wp-json\/wp\/v2\/posts\/80","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/austins.website\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/austins.website\/blog\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/austins.website\/blog\/wp-json\/wp\/v2\/comments?post=80"}],"version-history":[{"count":1,"href":"https:\/\/austins.website\/blog\/wp-json\/wp\/v2\/posts\/80\/revisions"}],"predecessor-version":[{"id":92,"href":"https:\/\/austins.website\/blog\/wp-json\/wp\/v2\/posts\/80\/revisions\/92"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/austins.website\/blog\/wp-json\/wp\/v2\/media\/81"}],"wp:attachment":[{"href":"https:\/\/austins.website\/blog\/wp-json\/wp\/v2\/media?parent=80"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/austins.website\/blog\/wp-json\/wp\/v2\/categories?post=80"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/austins.website\/blog\/wp-json\/wp\/v2\/tags?post=80"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}