{"id":9679,"date":"2026-03-28T06:36:02","date_gmt":"2026-03-28T06:36:02","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/prefetch\/"},"modified":"2026-03-28T06:36:02","modified_gmt":"2026-03-28T06:36:02","slug":"prefetch","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/prefetch\/","title":{"rendered":"Prefetch: What It Is, Key Features, Benefits, Use Cases, and How It Fits in SEO"},"content":{"rendered":"\n

Prefetch is a performance technique that proactively fetches resources a user is likely to need next\u2014before they click or navigate. In Organic Marketing<\/strong>, where success depends on earning attention rather than buying it, faster experiences reduce friction across the entire customer journey, from content discovery to conversion. In SEO<\/strong>, Prefetch is one of the practical levers that can help improve real user performance signals, engagement, and the overall quality of the on-site experience.<\/p>\n\n\n\n

Modern Organic Marketing strategies compete on experience as much as content. When two pages answer the same query, the site that feels instant often wins more clicks, reads, sign-ups, and repeat visits. Prefetch is not a magic ranking trick, but it can make your site feel faster in the moments that matter\u2014especially on mobile networks and content-heavy sites.<\/p>\n\n\n\n

What Is Prefetch?<\/h2>\n\n\n\n

Prefetch<\/strong> is a method of requesting and downloading resources (or even entire pages, depending on the approach) ahead of time<\/em>, based on predicted user navigation. The goal is to have those resources ready in the browser cache so that the next page or interaction loads faster.<\/p>\n\n\n\n

At its core, Prefetch is about anticipation<\/strong>:<\/p>\n\n\n\n

    \n
  • Predict what a user will do next (e.g., click a \u201cRead next\u201d article).<\/li>\n
  • Fetch the likely-needed assets in the background when the network is idle.<\/li>\n
  • Reduce wait time when the user actually navigates.<\/li>\n<\/ul>\n\n\n\n

    The business meaning is straightforward: Prefetch can increase the number of satisfied sessions by reducing load delays that cause abandonment. In Organic Marketing<\/strong>, that can translate to better content consumption, more pages per session, stronger newsletter growth, and improved conversion rate from non-paid traffic. In SEO<\/strong>, Prefetch supports better user experience and can contribute to improved performance metrics that search engines increasingly care about.<\/p>\n\n\n\n

    Why Prefetch Matters in Organic Marketing<\/h2>\n\n\n\n

    In Organic Marketing<\/strong>, you usually can\u2019t control when a user arrives, what device they\u2019re on, or how patient they are. Prefetch helps you control what happens after<\/em> arrival by improving the perceived speed of key paths like:<\/p>\n\n\n\n

      \n
    • Search landing page \u2192 category page <\/li>\n
    • Blog post \u2192 related post <\/li>\n
    • Product page \u2192 cart \u2192 checkout <\/li>\n
    • Feature page \u2192 pricing \u2192 signup<\/li>\n<\/ul>\n\n\n\n

      Strategically, Prefetch matters because it strengthens the \u201cmiddle of the funnel\u201d experience for organic visitors. Faster transitions encourage exploration, which is often how organic sessions become high-intent sessions.<\/p>\n\n\n\n

      From a competitive standpoint, Prefetch is one of the few technical improvements that can produce a noticeable experience advantage without changing your content strategy. While content and links remain foundational in SEO<\/strong>, performance and usability influence how well that content converts\u2014and how strongly users engage with it.<\/p>\n\n\n\n

      How Prefetch Works<\/h2>\n\n\n\n

      Prefetch is partly technical and partly behavioral. In practice, it works best when you combine smart triggers<\/strong> with careful constraints<\/strong> so you don\u2019t waste bandwidth or hurt Core Web Vitals.<\/p>\n\n\n\n

      A practical workflow looks like this:<\/p>\n\n\n\n

        \n
      1. \n

        Trigger (prediction)<\/strong>\n – The browser or your site predicts the next likely navigation.\n – Triggers might include: a link appearing in the viewport, a user hovering a link, a high-probability \u201cnext step\u201d (like a pagination link), or a known funnel path.<\/p>\n<\/li>\n

      2. \n

        Decision (rules and conditions)<\/strong>\n – Your implementation checks conditions such as:<\/p>\n

          \n
        • Is the network fast enough?<\/li>\n
        • Is the device memory constrained?<\/li>\n
        • Is the user in data-saver mode?<\/li>\n
        • Is the browser idle?<\/li>\n
        • This is where Prefetch becomes responsible rather than aggressive.<\/li>\n<\/ul>\n<\/li>\n
        • \n

          Execution (fetch in the background)<\/strong>\n – The browser downloads the specified resource(s) with low priority (typically \u201cwhen idle\u201d).\n – Resources may include HTML, JSON data used to render a route, images, fonts, CSS, or scripts\u2014depending on your setup.<\/p>\n<\/li>\n

        • \n

          Outcome (cache and faster navigation)<\/strong>\n – If the user takes the predicted action, the next page can load faster because assets are already cached.\n – If the user doesn\u2019t, the prefetch work may be wasted\u2014so measurement and restraint matter.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

          In SEO<\/strong> and Organic Marketing<\/strong>, the key is not \u201cprefetch everything,\u201d but \u201cprefetch what improves the experience for the paths that organic users actually take.\u201d<\/p>\n\n\n\n

          Key Components of Prefetch<\/h2>\n\n\n\n

          A solid Prefetch approach usually involves the following elements:<\/p>\n\n\n\n

          Resource hinting and routing logic<\/h3>\n\n\n\n

          You need a way to define what<\/em> to fetch. That may be a simple list of high-likelihood next pages (e.g., \u201crelated posts\u201d) or a more dynamic approach where your frontend framework prefetches data for links in view.<\/p>\n\n\n\n

          Caching layers<\/h3>\n\n\n\n

          Prefetch only helps if the fetched content is stored and reusable:<\/p>\n\n\n\n

            \n
          • Browser cache and HTTP caching headers<\/li>\n
          • Service worker caches (if you use a progressive web app approach)<\/li>\n
          • CDN caching for static assets<\/li>\n<\/ul>\n\n\n\n

            Performance governance<\/h3>\n\n\n\n

            Because Prefetch can increase total requests and bytes, teams need guardrails:<\/p>\n\n\n\n

              \n
            • Only prefetch on fast connections<\/li>\n
            • Limit prefetch to top-priority journeys<\/li>\n
            • Avoid prefetching on initial page load if it competes with critical resources<\/li>\n<\/ul>\n\n\n\n

              Measurement and monitoring<\/h3>\n\n\n\n

              To ensure Prefetch improves outcomes for Organic Marketing<\/strong> and SEO<\/strong>, you need to measure:<\/p>\n\n\n\n

                \n
              • Real user performance (field data)<\/li>\n
              • Navigation speed improvements<\/li>\n
              • Whether Prefetch increases wasted bytes or errors<\/li>\n<\/ul>\n\n\n\n

                Types of Prefetch<\/h2>\n\n\n\n

                \u201cPrefetch\u201d is often used broadly, but in real implementations there are several important distinctions. Understanding these helps you choose the right technique for your SEO<\/strong> and Organic Marketing goals.<\/p>\n\n\n\n

                Link\/resource prefetch (low-priority fetching)<\/h3>\n\n\n\n

                This is the classic idea: fetch a resource the user might need later, typically at low priority, often when the browser is idle. It\u2019s best for non-critical assets that will likely be used soon.<\/p>\n\n\n\n

                DNS prefetch (name resolution ahead of time)<\/h3>\n\n\n\n

                DNS prefetch resolves a domain name before a request is made. This can help when your page will load resources from third-party domains (fonts, APIs, embedded services). It doesn\u2019t download the resource\u2014it reduces the setup time.<\/p>\n\n\n\n

                Preconnect (early connection setup)<\/h3>\n\n\n\n

                Preconnect goes further than DNS and warms up the connection (DNS + TCP + TLS). It can improve speed for critical third-party origins, but overuse can create unnecessary connection overhead.<\/p>\n\n\n\n

                Data prefetch (application-level)<\/h3>\n\n\n\n

                Many modern sites fetch route data or API responses before navigation. For example, a content site might prefetch JSON for the next article card. This can make transitions feel instant even if the HTML isn\u2019t prefetched.<\/p>\n\n\n\n

                Speculative prefetch and prerender (more aggressive)<\/h3>\n\n\n\n

                Some modern approaches support speculative rules that can fetch or even render pages before navigation. This can be powerful, but it\u2019s easier to waste bandwidth and it requires stricter governance\u2014especially for authenticated, personalized, or frequently changing pages.<\/p>\n\n\n\n

                Real-World Examples of Prefetch<\/h2>\n\n\n\n

                1) Editorial content hub improving \u201cnext article\u201d clicks<\/h3>\n\n\n\n

                A publisher invests in Organic Marketing by building topic hubs. Readers often click the first related article under the fold. Prefetching the next-article data (and key assets like the hero image) when the related module enters the viewport can reduce the time between clicks and content display. For SEO<\/strong>, this can boost engagement metrics like pages per session and reduce pogo-sticking.<\/p>\n\n\n\n

                2) SaaS blog \u2192 feature page \u2192 pricing path<\/h3>\n\n\n\n

                A SaaS company attracts organic traffic via educational posts. Analytics shows a frequent journey from blog posts to a feature page, then pricing. Prefetching the pricing page\u2019s critical data (or route bundle) after the user spends, say, 15\u201320 seconds on a qualifying blog post can make the intent moment smoother. This supports Organic Marketing goals by lifting trial starts without changing rankings.<\/p>\n\n\n\n

                3) Ecommerce category \u2192 product detail navigation<\/h3>\n\n\n\n

                For high-performing categories, users often open a product detail page after scanning a grid. Prefetching the product detail route assets on link hover (or when a product card is near the pointer on desktop) can speed up navigation. In SEO<\/strong>, faster product page loads can improve user satisfaction and reduce abandonment from organic category landings.<\/p>\n\n\n\n

                Benefits of Using Prefetch<\/h2>\n\n\n\n

                When implemented carefully, Prefetch can deliver meaningful gains:<\/p>\n\n\n\n

                  \n
                • Faster perceived performance:<\/strong> Next-page navigations feel near-instant because assets are ready.<\/li>\n
                • Better user experience for organic visitors:<\/strong> Organic Marketing thrives when visitors explore; Prefetch reduces friction between steps.<\/li>\n
                • Higher conversion efficiency:<\/strong> Smoother transitions in funnels can improve signup, add-to-cart, and lead form completion rates.<\/li>\n
                • Potential Core Web Vitals support:<\/strong> By reducing work at navigation time, Prefetch can indirectly help metrics like LCP and INP in real user conditions.<\/li>\n
                • Operational leverage:<\/strong> Performance improvements can compound across content libraries and product catalogs without rewriting every page.<\/li>\n<\/ul>\n\n\n\n

                  Challenges of Prefetch<\/h2>\n\n\n\n

                  Prefetch is not \u201cfree speed.\u201d It comes with real trade-offs:<\/p>\n\n\n\n

                    \n
                  • Wasted bandwidth:<\/strong> If predictions are wrong, you download resources users never use\u2014especially costly on mobile data.<\/li>\n
                  • Competition with critical resources:<\/strong> Aggressive Prefetch can slow the current page if it steals network bandwidth from essential assets.<\/li>\n
                  • Caching complexity:<\/strong> Poor caching headers, personalization, or frequent content updates can reduce cache usefulness.<\/li>\n
                  • Analytics side effects:<\/strong> Some forms of prefetch\/prerender can complicate pageview counting or event timing if instrumentation isn\u2019t careful.<\/li>\n
                  • Privacy and consent considerations:<\/strong> Prefetching third-party resources can create early connections to external services; governance must respect consent models and regional privacy expectations.<\/li>\n<\/ul>\n\n\n\n

                    For SEO<\/strong> and Organic Marketing teams, the biggest risk is implementing Prefetch \u201cbecause it\u2019s performance\u201d without validating that it improves key journeys for organic users.<\/p>\n\n\n\n

                    Best Practices for Prefetch<\/h2>\n\n\n\n

                    Use these practices to make Prefetch reliable and measurable:<\/p>\n\n\n\n

                      \n
                    1. \n

                      Start with journey data<\/strong>\n – Identify the top organic landing pages and the most common next clicks (from analytics and behavior flows).\n – Prefetch only for high-probability paths.<\/p>\n<\/li>\n

                    2. \n

                      Use conservative triggers<\/strong>\n – Favor triggers like \u201clink in viewport\u201d or \u201cafter user engagement time.\u201d\n – Use hover-based Prefetch cautiously; it can fire unintentionally on touch devices.<\/p>\n<\/li>\n

                    3. \n

                      Respect network and device constraints<\/strong>\n – Avoid Prefetch on slow connections, low-memory devices, or when data-saver is enabled.\n – Prioritize accessibility and stability over micro-optimizations.<\/p>\n<\/li>\n

                    4. \n

                      Don\u2019t prefetch what won\u2019t cache<\/strong>\n – Ensure caching rules allow reuse.\n – Avoid prefetching highly personalized pages unless you\u2019re prefetching only shared assets.<\/p>\n<\/li>\n

                    5. \n

                      Limit scope and concurrency<\/strong>\n – Set caps (e.g., only prefetch the top 1\u20133 likely next pages).\n – Avoid \u201cprefetch storms\u201d on pages with many links (like mega menus).<\/p>\n<\/li>\n

                    6. \n

                      Validate with real user monitoring<\/strong>\n – Lab tests are useful, but field data tells you whether Prefetch helps real organic visitors and doesn\u2019t worsen Core Web Vitals.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

                      Tools Used for Prefetch<\/h2>\n\n\n\n

                      Prefetch itself is implemented in your frontend and infrastructure, but several tool categories help you manage it within SEO<\/strong> and Organic Marketing<\/strong>:<\/p>\n\n\n\n

                        \n
                      • Browser developer tools:<\/strong> Inspect network priority, cache usage, and whether prefetched resources are reused.<\/li>\n
                      • Lab performance testing tools:<\/strong> Run repeatable tests to compare navigation speed with and without Prefetch.<\/li>\n
                      • Real user monitoring (RUM):<\/strong> Measure actual LCP\/INP and navigation timing by device, network, and landing page.<\/li>\n
                      • Analytics platforms:<\/strong> Identify high-probability next clicks from organic landings and quantify conversion lift.<\/li>\n
                      • SEO auditing tools:<\/strong> Surface performance issues, over-heavy pages, and opportunities to improve technical experience for organic visitors.<\/li>\n
                      • Tag management and event tracking systems:<\/strong> Ensure events are measured correctly when navigation becomes faster or is influenced by speculative loading.<\/li>\n<\/ul>\n\n\n\n

                        Metrics Related to Prefetch<\/h2>\n\n\n\n

                        To evaluate Prefetch properly, track metrics that reflect both performance and business outcomes:<\/p>\n\n\n\n

                        Performance metrics (user experience)<\/h3>\n\n\n\n
                          \n
                        • LCP (Largest Contentful Paint):<\/strong> Can improve if next page\u2019s critical assets are ready.<\/li>\n
                        • INP (Interaction to Next Paint):<\/strong> Faster transitions can reduce interaction delay perception.<\/li>\n
                        • Navigation timing:<\/strong> Time from click to next page render (field-measured when possible).<\/li>\n
                        • Cache hit ratio:<\/strong> How often prefetched assets are actually reused.<\/li>\n<\/ul>\n\n\n\n

                          Efficiency metrics (cost and waste)<\/h3>\n\n\n\n
                            \n
                          • Prefetch utilization rate:<\/strong> Percentage of prefetched resources that are later used.<\/li>\n
                          • Wasted bytes:<\/strong> Data downloaded via Prefetch that never contributed to a user action.<\/li>\n
                          • Request count impact:<\/strong> Additional network requests introduced by Prefetch.<\/li>\n<\/ul>\n\n\n\n

                            Organic Marketing and SEO outcome metrics<\/h3>\n\n\n\n
                              \n
                            • Bounce rate \/ engagement rate (context-dependent):<\/strong> Look for improved engagement from organic landings.<\/li>\n
                            • Pages per session and scroll depth:<\/strong> Prefetch can encourage exploration on content sites.<\/li>\n
                            • Conversion rate for organic sessions:<\/strong> Trials, leads, purchases, or micro-conversions.<\/li>\n
                            • Return visitor rate:<\/strong> Better experiences can improve brand preference over time.<\/li>\n<\/ul>\n\n\n\n

                              Future Trends of Prefetch<\/h2>\n\n\n\n

                              Prefetch is evolving from simple link hints to more intelligent, policy-aware speculation:<\/p>\n\n\n\n

                                \n
                              • Smarter speculation rules:<\/strong> Browsers are moving toward more standardized ways to declare \u201clikely next navigations,\u201d enabling safer, more consistent Prefetch behavior.<\/li>\n
                              • AI-assisted prediction:<\/strong> On-site models (or rule-based systems informed by analytics) can personalize Prefetch decisions by device type, entry intent, and historical paths\u2014especially relevant for Organic Marketing funnels.<\/li>\n
                              • Privacy-first constraints:<\/strong> Expect stricter controls and clearer user choice signals (like data-saver, consent states) that limit when Prefetch should occur.<\/li>\n
                              • Greater focus on field performance:<\/strong> As measurement improves, teams will optimize Prefetch based on real user segments (organic vs. email vs. direct) rather than averages.<\/li>\n
                              • Integration with edge delivery:<\/strong> CDNs and edge logic can complement Prefetch by reducing latency and improving cacheability, strengthening technical foundations for SEO<\/strong>.<\/li>\n<\/ul>\n\n\n\n

                                Prefetch vs Related Terms<\/h2>\n\n\n\n

                                Prefetch vs Preload<\/h3>\n\n\n\n

                                Preload<\/strong> is about fetching critical<\/em> resources needed for the current page as soon as possible. Prefetch<\/strong> is about future<\/em> resources that might be needed next. In SEO<\/strong> work, preload is often used to improve above-the-fold speed, while Prefetch targets faster subsequent navigations.<\/p>\n\n\n\n

                                Prefetch vs Prerender<\/h3>\n\n\n\n

                                Prerender<\/strong> goes beyond downloading\u2014it can render the next page in advance so it appears instantly on navigation. It can be more powerful than Prefetch, but it\u2019s also riskier (more CPU, more memory, more wasted work if the user doesn\u2019t navigate). Use it only for extremely high-confidence journeys.<\/p>\n\n\n\n

                                Prefetch vs Caching<\/h3>\n\n\n\n

                                Caching is the general strategy of storing resources to reuse later. Prefetch<\/strong> is one way to populate<\/em> the cache proactively. You can have excellent caching without Prefetch, and you can implement Prefetch poorly if caching headers and invalidation aren\u2019t handled well.<\/p>\n\n\n\n

                                Who Should Learn Prefetch<\/h2>\n\n\n\n

                                Prefetch sits at the intersection of performance, product, and growth, so it\u2019s useful for multiple roles:<\/p>\n\n\n\n

                                  \n
                                • Marketers:<\/strong> Understand how Prefetch supports Organic Marketing outcomes like engagement and conversions from organic traffic.<\/li>\n
                                • SEO specialists:<\/strong> Evaluate Prefetch as part of technical SEO and user experience improvements, especially for large sites.<\/li>\n
                                • Analysts:<\/strong> Measure whether Prefetch actually improves funnels, not just lab scores.<\/li>\n
                                • Agencies:<\/strong> Identify high-impact navigation paths and create implementation roadmaps clients can maintain.<\/li>\n
                                • Business owners and founders:<\/strong> Prioritize performance work that improves conversion efficiency from non-paid channels.<\/li>\n
                                • Developers:<\/strong> Implement Prefetch safely with network-aware rules, caching discipline, and reliable measurement.<\/li>\n<\/ul>\n\n\n\n

                                  Summary of Prefetch<\/h2>\n\n\n\n

                                  Prefetch is a technique for proactively fetching likely next resources to make navigation feel faster. In Organic Marketing<\/strong>, it reduces friction for visitors who arrive from search and then explore deeper into your content or product journey. In SEO<\/strong>, Prefetch supports a stronger user experience and can contribute to better real-world performance signals, higher engagement, and improved conversion efficiency\u2014when applied selectively and measured carefully.<\/p>\n\n\n\n

                                  Frequently Asked Questions (FAQ)<\/h2>\n\n\n\n

                                  What is Prefetch and when should I use it?<\/h3>\n\n\n\n

                                  Prefetch is the practice of fetching likely next resources in the background so future navigations load faster. Use it on high-probability paths (related content, next steps in a funnel) and avoid it on low-confidence links or bandwidth-constrained users.<\/p>\n\n\n\n

                                  Does Prefetch directly improve SEO rankings?<\/h3>\n\n\n\n

                                  Prefetch is not a direct ranking factor by itself. However, it can improve user experience and real-world performance, which can support SEO<\/strong> outcomes like better engagement and more successful sessions from organic traffic.<\/p>\n\n\n\n

                                  Can Prefetch hurt performance?<\/h3>\n\n\n\n

                                  Yes. If you prefetch too much or at the wrong time, it can compete with critical resources, increase total bytes downloaded, and waste bandwidth\u2014especially on mobile networks.<\/p>\n\n\n\n

                                  Should I prefetch entire pages or just data\/assets?<\/h3>\n\n\n\n

                                  It depends on your architecture. Prefetching route data or critical assets can deliver most of the benefit with less waste. Prefetching entire pages (or prerendering) can be faster but requires higher confidence and stricter controls.<\/p>\n\n\n\n

                                  How do I measure whether Prefetch is working?<\/h3>\n\n\n\n

                                  Track navigation speed (click-to-render), cache hit ratio, Prefetch utilization rate, and conversion metrics for organic sessions. Validate improvements using real user monitoring, not only lab tests.<\/p>\n\n\n\n

                                  Is Prefetch useful for Organic Marketing beyond blogs?<\/h3>\n\n\n\n

                                  Yes. Prefetch can improve funnels across SaaS, ecommerce, marketplaces, and publishers\u2014anywhere organic visitors take predictable next steps (pricing, signup, product detail, cart, comparisons).<\/p>\n\n\n\n

                                  What\u2019s the safest place to start with Prefetch?<\/h3>\n\n\n\n

                                  Start with one or two high-traffic organic landing templates and prefetch only the most common next click. Add network\/device constraints and measure both performance and Organic Marketing outcomes before expanding.<\/p>\n","protected":false},"excerpt":{"rendered":"

                                  Prefetch is a performance technique that proactively fetches resources a user is likely to need next\u2014before they click or navigate. In **Organic Marketing**, where success depends on earning attention rather than buying it, faster experiences reduce friction across the entire customer journey, from content discovery to conversion. In **SEO**, Prefetch is one of the practical levers that can help improve real user performance signals, engagement, and the overall quality of the on-site experience.<\/p>\n","protected":false},"author":10235,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[131],"tags":[],"class_list":["post-9679","post","type-post","status-publish","format-standard","hentry","category-seo"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/9679","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/users\/10235"}],"replies":[{"embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/comments?post=9679"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/9679\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=9679"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=9679"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=9679"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}