{"id":2276,"date":"2023-12-26T10:42:13","date_gmt":"2023-12-26T10:42:13","guid":{"rendered":"https:\/\/crowdo.net\/blog\/?p=2276"},"modified":"2025-01-27T16:23:07","modified_gmt":"2025-01-27T16:23:07","slug":"canonical-urls","status":"publish","type":"post","link":"https:\/\/crowdo.net\/blog\/canonical-urls\/","title":{"rendered":"How Canonical URLs Improve Your SEO"},"content":{"rendered":"    <div class=\"quote-box\">\r\n        <div><p>The same blog post and product pages showing up two, three, even ten times in <a href=\"https:\/\/crowdo.net\/blog\/organic-vs-paid-search\/\">search results<\/a>? While simply embarrassing at first glance, this duplicate content dilutes your site&#8217;s authority, tanks your SEO, and costs you conversions. \ud83d\udcc9 And no, deleting or <a href=\"https:\/\/crowdo.net\/blog\/301-redirects\/\">301 redirecting<\/a> pages one-by-one won&#8217;t cut it. Welcome your new best friend&#8230;canonical URLs!<\/p>\n<\/div>\r\n    <\/div>\n\n\n<h2 class=\"wp-block-heading\">What Are Canonical URLs<\/h2>\n\n\n\n<p>What is a canonical URL? Imagine you craft a masterpiece blog post packed with grade-A advice. But when you publish, whoops &#8211; the CMS accidentally outputs 3 duplicate copies inheriting differing URLs!<\/p>\n\n\n\n<p>Now, adoring fans share and link to all variants, not realizing they mirror each other. Signals split, metrics get fractured, authority leeches away bit by bit as the perfect post gets shredded into confusing echo chambers&#8230;\ud83d\ude31<\/p>\n\n\n\n<p>Luckily, canonical URLs burst onto the scene like superhero capes to combat this duplicate dilutive disaster!<\/p>\n\n\n\n<p>As the <em>master page<\/em> coordinates duplicates under its cape, canonical URLs consolidate and beam all the hard-earned SEO signals directly into a primary destination target. No more leakage across fractured derivative copies. Just one channel capturing the full spotlight!<\/p>\n\n\n\n<p>So, what <em>are<\/em> these duplicate-fighting canonical tags exactly?<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">URLs as Identity System<\/h3>\n\n\n\n<p>To understand canonicals, we first have to step into a crawler bot&#8217;s shoes as it scans an unknown site for the first time. <em>Beep bop boop<\/em> goes its robotic brain digesting URL paths into semantic site understanding.<\/p>\n\n\n\n<p><em>\/<em>products<\/em>\/shirts<\/em> signals a different content identity than <em>\/<em>collection<\/em>\/shirts<\/em> based on folder structure alone. URLs act as the content equivalents of social security numbers &#8211; unique IDs for bots to grasp page meaning.<\/p>\n\n\n\n<p>Now imagine the same Navy Blue t-shirt showing up under two URLs:<\/p>\n\n\n\n<p><em>\/products\/shirts<\/em><\/p>\n\n\n\n<p><em>\/collection\/shirts<\/em><\/p>\n\n\n\n<p>The bot double takes hard, potentially perceiving duplicate spam tactics afoot! <em>Is this site trying to dupe us into higher rankings?<\/em> \u26a0\ufe0f<\/p>\n\n\n\n<p>Without a canonical tag, the bot loses context vital for proper page interpretation.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Clarifying Context for Bots<\/h3>\n\n\n\n<p>Canonical URLs provide missing orientation for search bot understanding when inadvertent duplicates emerge:<\/p>\n\n\n\n<p><em>&#8220;Hey Google! We know this content repeats under two categories. Don&#8217;t penalize us! Just follow the canonical URL we recommend as the primary identity for this page in your systems.&#8221;<\/em> \ud83e\udd16\ud83d\udc4d<\/p>\n\n\n\n<p>The tag doesn&#8217;t redirect users or block alternate access. But for crawling prioritization, it declares the target destination for indexing.<\/p>\n\n\n\n<p>This clarifying context resolves confusion across parameters, paths, case variations, http vs https duplicates &#8211; funneling similarity into a singular canonical page.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why Canonicalization Is Important For SEO<\/h2>\n\n\n\n<p>Though easily dismissed as niche fine print, canonical URLs form foundational pillars for SEO stability:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Duplicate Content Crisis Aversion<\/h3>\n\n\n\n<p><strong>\ud83d\udd26 Flashback to early 2000s search spam tactics:<\/strong><\/p>\n\n\n\n<p>Underground forums burst with tips for scrappy SEOs to auto-generate hundreds of doorway pages copying and mirroring similar content.<\/p>\n\n\n\n<p><em>&#8220;More pages about &#8216;Nike shoes&#8217; means more Nike rankings, folks!&#8221;<\/em> Misguided but economically rational at the tiny scale of early <a href=\"https:\/\/crowdo.net\/blog\/best-search-engines\/\">engines<\/a>. \ud83d\udc5f<\/p>\n\n\n\n<p>The duplicate content deluge left search indexes polluted like overflowing landfills. Unable to orient signal importance between originals vs mirrors, poor crawler bots would get lost in funhouses of duplication, fruitlessly trying to surface the pearls of original content&#8230;\ud83d\uddd1\ufe0f<\/p>\n\n\n\n<p><strong>Enter canonical URLs &#8211; the indexing cleanup crew!<\/strong> \ud83c\udf1f<\/p>\n\n\n\n<p>Their emergence finally gave search confidence in site intentions, consolidating duplicates crisply under preferred URLs:<\/p>\n\n\n\n<p><em>&#8220;We&#8217;re NOT deliberately duplicating content across these URLs &#8211; just index our suggested canonical master page, please!&#8221;<\/em> \ud83d\ude4f<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Consolidating Authority Signals<\/h3>\n\n\n\n<p>Before canonicals stepped onto the scene, duplicate content spread link equity, social signals, and engagement thinly across multiple URLs.<\/p>\n\n\n\n<p>Rather than a single URL basking under the glow of the full authority signals pointing to its content, duplicates fractured and diluted credit.<\/p>\n\n\n\n<p>Canonical tags for SEO nourish wholeness from separated fractures. As the URL ambassador coordinating duplicates, canonicals funnel all isolated metrics channels into one screen-dominating marquee promoting content to the max! \ud83c\udf1f.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Optimizing Limited Crawler Budget<\/h3>\n\n\n\n<p>Google enjoys essentially infinite server farms to fuel their authoritarian crawler scale. But even Mighty Google must diligently prioritize budgets across the infinitely evolving web.<\/p>\n\n\n\n<p>Accidentally re-crawling duplicate content squanders precious resources. Multiply that waste at scale, and you limit the marginal coverage of new quality pages.<\/p>\n\n\n\n<p>Canonicals provide orientation for more optimized crawl analysis based purely on fresh or revised pages. The cascading compound effect over cycles? Vastly expanded reach and scale at the margins&#8230;\ud83d\udc4c<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How To Implement Canonical Tags<\/h2>\n\n\n\n<p>So you&#8217;re convinced of the SEO superpowers unlocked by canonical URLs. But how do you actually start structuring these duplicate-consolidating tags across a complex website? Rolling out canonicals effectively takes a combination of:<\/p>\n\n\n\n<ul>\n<li>Technical prowess<\/li>\n\n\n\n<li>Architectural sleuthing<\/li>\n\n\n\n<li>Structured testing<\/li>\n<\/ul>\n\n\n\n<p>&#8230;with a dash of quirky creativity sprinkled on top!<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Gather Initial Site Recon<\/h3>\n\n\n\n<p>The first step of implementation requires information gathering across two fronts:<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Surface Current Duplicates<\/h4>\n\n\n\n<p>Time to flex those cybersecurity muscles! \ud83d\udcaa You&#8217;ll need to crawl across your site architecture meticulously to surface <em>all<\/em> current duplication scenarios.<\/p>\n\n\n\n<p>Common suspects include:<\/p>\n\n\n\n<ul>\n<li>Varying URL parameters<\/li>\n\n\n\n<li>Differing internal paths<\/li>\n\n\n\n<li>HTTP vs HTTPS versions<\/li>\n\n\n\n<li>Domain aliases<\/li>\n<\/ul>\n\n\n\n<p>Uncover all duplicate content occurrences currently diluting metrics across multiple URLs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Audit Site Architecture<\/h3>\n\n\n\n<p>Secondly, comprehensively audit technical specifications like:<\/p>\n\n\n\n<ul>\n<li>CMS or site-building platform<\/li>\n\n\n\n<li>Server type and configuration<\/li>\n\n\n\n<li>Current hosting stack<\/li>\n<\/ul>\n\n\n\n<p>This equips you with the info needed to insert canonical tags accurately based on the environment.<\/p>\n\n\n\n<p>Got all that? Great, let&#8217;s continue.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Select Target Canonical URLs<\/h3>\n\n\n\n<p>Next, decide on appropriate canonical URLs you want search engines to prioritize for duplicate content.<\/p>\n\n\n\n<p><strong>Tips for selection:<\/strong><\/p>\n\n\n\n<ul>\n<li>Choose URLs with the cleanest parameters<\/li>\n\n\n\n<li>Prefer URLs with the most relevant categories<\/li>\n\n\n\n<li>Consider migration planning if restructuring paths<\/li>\n\n\n\n<li>Avoid targeting temporary pages like sales or seasonal events<\/li>\n<\/ul>\n\n\n\n<p>Assign each surfaced duplicate to a relevant canonical URL target.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Insert Canonical Tags<\/h3>\n\n\n\n<p>Now, the fun part &#8211; actual implementation!<\/p>\n\n\n\n<p>You have two options for placing canonical tags:<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">#1 HTML Link Tags<\/h4>\n\n\n\n<p>Easily add link tags within &lt;head&gt; of page HTML:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&lt;link rel=\"canonical\" href=\"https:\/\/target-url.com\"&gt;<\/code><\/pre>\n\n\n\n<p><strong>Pros:<\/strong><\/p>\n\n\n\n<ul>\n<li>Simple to deploy across many pages<\/li>\n\n\n\n<li>Direct alignment with target URLs<\/li>\n<\/ul>\n\n\n\n<p><strong>Cons<\/strong>:<\/p>\n\n\n\n<ul>\n<li>Can get messy with tons of pages<\/li>\n\n\n\n<li>Risk of team players forgetting to add them<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">#2 Server-side via HTTP Headers<\/h4>\n\n\n\n<p>Programmatically send via HTTP response headers:<\/p>\n\n\n\n<p>Link: &lt;https:\/\/target-url.com&gt;; rel=&#8221;canonical&#8221;<\/p>\n\n\n\n<p><strong>Pros:<\/strong><\/p>\n\n\n\n<ul>\n<li>Centralized management<\/li>\n\n\n\n<li>Handle redirects\/rewrites behind the scenes<\/li>\n<\/ul>\n\n\n\n<p><strong>Cons:<\/strong><\/p>\n\n\n\n<ul>\n<li>Increased dev lift<\/li>\n\n\n\n<li>Still need testing\/QA<\/li>\n<\/ul>\n\n\n\n<p>Choose the method that fits your stack and resources.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Test Canonical Rollout<\/h3>\n\n\n\n<p>Once inserted, rigorously test that:<\/p>\n\n\n\n<p>\ud83d\udd0e Target canonical URLs are loading as expected<\/p>\n\n\n\n<p>\ud83d\udd2c Specified tags are accurately displayed on duplicate URLs<\/p>\n\n\n\n<p>\ud83d\udd0d Crawler tools show consolidation under the target URL<\/p>\n\n\n\n<p>Refine any issues before the full launch!<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Track Impact Ongoing<\/h3>\n\n\n\n<p>Moving forward, track that canonical changes yield intended results:<\/p>\n\n\n\n<p>\ud83d\udcc8 Consolidated rankings for target URLs<\/p>\n\n\n\n<p>\ud83d\udcc9 Lower dilution metrics across duplicates<\/p>\n\n\n\n<p>\ud83d\udcca Increased overall site visibility<\/p>\n\n\n\n<p>Tune and iterate tags as needed!<\/p>\n\n\n\n<p>And enjoy your newfound SEO boost from structurally sound canonicals! \ud83d\ude80<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Google&#8217;s Approach to Canonical URLs<\/h2>\n\n\n\n<p>Google has refined their interpretation and utilization of canonical URLs enormously since first launching the concept back in 2009. Let&#8217;s explore key milestones in their canonical evolution journey:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Origin Story<\/h3>\n\n\n\n<p>Google introduced the idea of canonical URL meta tags in 2009 to address the persistent issue of duplicate content dilution across the web.<\/p>\n\n\n\n<p>As they described in announcing the move:<\/p>\n\n\n\n<p><em>&#8220;Site owners can now control the process of serving applicable content to search engines more effectively by consolidating signals that might get lost across URL variations.&#8221;<\/em><\/p>\n\n\n\n<p>The goal was to improve search quality by better consolidating metrics and signals pointing to the unique content in one place &#8211; avoiding fragmentation across unnecessary mirrors.<\/p>\n\n\n\n<p>Early experiments focused on use cases like:<\/p>\n\n\n\n<ul>\n<li>Case sensitive URLs<\/li>\n\n\n\n<li>HTTP vs HTTPS<\/li>\n\n\n\n<li>Trailing slashes<\/li>\n<\/ul>\n\n\n\n<p>The results in cleaning up duplication looked promising&#8230;<\/p>\n\n\n\n<p>But open questions remained about expanding scope.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Maturing Interpretation<\/h3>\n\n\n\n<p>Over the next 5+ years, Google increasingly normalized the adoption and range of canonical tags across the web.<\/p>\n\n\n\n<p>In 2012, they released expanded guidelines highlighting best practices like:<\/p>\n\n\n\n<ul>\n<li>Placing tags on indexable duplicate pages<\/li>\n\n\n\n<li>Pointing to live target URLs<\/li>\n\n\n\n<li>Not trying to manipulate rankings between domains<\/li>\n<\/ul>\n\n\n\n<p>The guidelines positioned canonicals as <em>&#8220;hints that help search engines consolidate useful signals and present better search results.&#8221;<\/em><\/p>\n\n\n\n<p>Google improved their parsing of tags and grew to support broader use cases like:<\/p>\n\n\n\n<ul>\n<li>Consolidating geo-targeted pages<\/li>\n\n\n\n<li>Merging subdomains into main domains<\/li>\n\n\n\n<li>Even consolidating equivalent images into preferred thumbnails.<\/li>\n<\/ul>\n\n\n\n<p>The infrastructure improved dramatically to handle an ever-wider range of duplication scenarios.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Refining Selection Logic<\/h3>\n\n\n\n<p>As canonical understanding and adoption spread, Google adapted their internal algorithms for assessing which version in a duplicate set to actually index and rank.<\/p>\n\n\n\n<p>Rather than automatically trusting a site&#8217;s self-declared canonical URL in all cases, additional factors emerged in selection logic:<\/p>\n\n\n\n<p>\ud83d\udd0e <strong>Page quality<\/strong> &#8211; the relevance and richness of <a href=\"https:\/\/crowdo.net\/blog\/web-content-writing-tips\/\">content<\/a><\/p>\n\n\n\n<p>\ud83d\udcc8 <strong>Popularity signals<\/strong> &#8211; <a href=\"https:\/\/crowdo.net\/blog\/buying-backlinks\/\">external links<\/a>\/engagement<\/p>\n\n\n\n<p>\ud83d\udcac <strong>User experience<\/strong> &#8211; mobile friendliness, <a href=\"https:\/\/crowdo.net\/blog\/page-speed\/\">speed<\/a><\/p>\n\n\n\n<p>This built further sophistication but required even more precise documentation&#8230;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Clarifying Official Guidelines<\/h3>\n\n\n\n<p>Balancing the improved automation and range of canonicalization, Google faced an expanding burden in clarifying guidelines and expectations around proper local URL consolidation.<\/p>\n\n\n\n<p>Today, their core advice centers around:<\/p>\n\n\n\n<ul>\n<li>Mapping duplicates clearly<\/li>\n\n\n\n<li>Pointing to live, relevant pages<\/li>\n\n\n\n<li>Using tags accurately based on URL format needs<\/li>\n\n\n\n<li>Not trying to manipulate search or deceive users<\/li>\n<\/ul>\n\n\n\n<p>Striking the right balance remains challenging. Google treads lightly, not wanting to over-optimize and consolidate away potentially useful content variations. But they continue working to isolate unhelpful duplication.<\/p>\n\n\n\n<p>The guidelines remain etched in the sand as new duplication forms arise across the endless web. But after 15+ years of maturing canonical systems, Google sits confidently atop robust infrastructure.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Future-Proofing Duplication Management<\/h3>\n\n\n\n<p>Looking ahead, expect Google to push new frontiers, expanding automated consolidation where possible across sites.<\/p>\n\n\n\n<p>Machine learning promises smarter models for detecting semantic duplication &#8211; images, videos, and snippets without needing explicit tagging in all cases. Reducing manual inputs expands the scalable reach.<\/p>\n\n\n\n<p>However, user understanding and intentions will continue to limit the scope. After all, not all duplication lacks utility from a human lens. Discerning signal from noise remains more art than science alone.<\/p>\n\n\n\n<p>The next 15 years of canonicalization promise an equally fascinating unfolding journey!<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Common Mistakes and Solutions<\/h2>\n\n\n\n<p>Even advanced SEO pros frequently trip up when first tiptoeing into canonical land \ud83d\ude16.<\/p>\n\n\n\n<p>Let&#8217;s shine some light on frequent canonicalization issues &amp; solutions to course correct faster than a SpaceX rocket! \ud83d\ude80\ud83c\udf1f<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Misdirected Mapping<\/h3>\n\n\n\n<p>A common early blunder is incorrectly mapping duplicate content pages onto target canonical URLs in the relationship diagramming stage:<\/p>\n\n\n\n<p><strong>\ud83e\udd26\u200d Mistake<\/strong>: Tagging \/shirt-mens.php?color=red to canonicalize onto \/pants-womens.php. <em>Totally illogical redirection!<\/em><\/p>\n\n\n\n<p><strong>\ud83e\udd13 Solution:<\/strong> Carefully audit content equivalency across duplicates before pointlessly sending signals to unrelated canonical targets.<\/p>\n\n\n\n<p>Double check\u2935\ufe0f Expected page consolidation \u2705 Actual redirected pages \ud83d\udd75\ufe0f\u200d\u2640\ufe0f<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Dead Links Danger<\/h3>\n\n\n\n<p>Another frequent flaw is pointing duplicate pages to <em>defunct or dead<\/em> canonical destination URLs:<\/p>\n\n\n\n<p><strong>\ud83e\udd26\u200d\u2640\ufe0f Mistake<\/strong>: Redirecting live&#8221;\/tops\/hoodies&#8221; to a 404-error dead link. <em>All aboard the crawler frustration train! \ud83d\ude82<\/em><\/p>\n\n\n\n<p><strong>\ud83e\udde0 Solution<\/strong>: Always verify target canonical links resolve properly before tagging dependencies. No one enjoys unexpected dead ends!<\/p>\n\n\n\n<p>Quick reference protocol &#8211; paste targets into browser address bars pre-tagging. If errors arise, redirect to an equivalent functioning page.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Misusing For Redirects<\/h3>\n\n\n\n<p>Attempting to directly <em>redirect<\/em> users from one URL to another via canonical tags also invites issues:<\/p>\n\n\n\n<p><strong>\ud83d\ude35\u200d\ud83d\udcab Mistake:<\/strong> Using rel=&#8221;canonical&#8221; like a 301 redirect to force \/page-a visitors to \/page-b.<\/p>\n\n\n\n<p><strong>\u26a0\ufe0f Warning<\/strong> &#8211; Canonicals only <em>suggest<\/em> preferred indexing URLs to engines without actually redirecting users!<\/p>\n\n\n\n<p><strong>\ud83d\udca1 Solution<\/strong>: Implement actual <a href=\"https:\/\/crowdo.net\/blog\/301-redirects\/\">301-redirect<\/a> logic on the web server for altering user flow between URLs. Keep canonicals focused purely on consolidation signals for bots.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Ignoring Self-Referencing<\/h3>\n\n\n\n<p>Finally, a tactical misstep we see periodically is failing to self-reference canonical tags on target pages:<\/p>\n\n\n\n<p><strong>\ud83e\udd28 Mistake<\/strong>: Adding canonical link tag ONLY on \/page-red pointing to \/page-blue but forgetting to also self-reference a canonical tag on \/page-blue pointing back to itself. <em>Asymmetry invites trouble!<\/em><\/p>\n\n\n\n<p><strong>\ud83d\udccbSolution<\/strong>: Any designated target canonical URLs should self-reference with their own rel=&#8221;canonical&#8221; link tags to reinforce consolidation on both ends &#8211; decreasing the chances of signals leaking away down the line due to oversight.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Wrap-up<\/h2>\n\n\n\n<p>At the end of the day, canonicalization comes back to thoughtful website information architecture with appropriate pointers to help both bots <em>and<\/em> visitors efficiently locate the good stuff!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Your website fighting with itself? Canonical tags end the duplicate content division. Learn how unified signals concentrate into SEO heroes.<\/p>","protected":false},"author":3,"featured_media":2303,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[9],"tags":[],"acf":[],"_links":{"self":[{"href":"https:\/\/crowdo.net\/blog\/wp-json\/wp\/v2\/posts\/2276"}],"collection":[{"href":"https:\/\/crowdo.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/crowdo.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/crowdo.net\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/crowdo.net\/blog\/wp-json\/wp\/v2\/comments?post=2276"}],"version-history":[{"count":2,"href":"https:\/\/crowdo.net\/blog\/wp-json\/wp\/v2\/posts\/2276\/revisions"}],"predecessor-version":[{"id":2280,"href":"https:\/\/crowdo.net\/blog\/wp-json\/wp\/v2\/posts\/2276\/revisions\/2280"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/crowdo.net\/blog\/wp-json\/wp\/v2\/media\/2303"}],"wp:attachment":[{"href":"https:\/\/crowdo.net\/blog\/wp-json\/wp\/v2\/media?parent=2276"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/crowdo.net\/blog\/wp-json\/wp\/v2\/categories?post=2276"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/crowdo.net\/blog\/wp-json\/wp\/v2\/tags?post=2276"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}