{"id":7125,"date":"2026-03-24T01:13:18","date_gmt":"2026-03-24T01:13:18","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/conversion-blockers\/"},"modified":"2026-03-24T01:13:18","modified_gmt":"2026-03-24T01:13:18","slug":"conversion-blockers","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/conversion-blockers\/","title":{"rendered":"Conversion Blockers: What It Is, Key Features, Benefits, Use Cases, and How It Fits in CRO"},"content":{"rendered":"\n

Conversion Blockers are anything that prevents a user from completing a desired action\u2014buying, subscribing, requesting a demo, downloading a resource, or even progressing to the next step in a funnel. In Conversion & Measurement<\/strong>, they show up as unexplained drop-offs, poor form completion, rising acquisition costs, or \u201cgood traffic\u201d that doesn\u2019t turn into outcomes. In CRO<\/strong>, they are the friction points you identify, prioritize, and remove to unlock more revenue from the same demand.<\/p>\n\n\n\n

Conversion Blockers matter more than ever because modern journeys are complex: multiple devices, privacy constraints, slower networks, ad fatigue, and rising user expectations. A strong Conversion & Measurement<\/strong> strategy doesn\u2019t just report conversion rates\u2014it helps you diagnose why conversions don\u2019t happen. That\u2019s exactly where Conversion Blockers become a practical, cross-functional focus area for marketing, product, analytics, and engineering.<\/p>\n\n\n\n

What Is Conversion Blockers?<\/h2>\n\n\n\n

Conversion Blockers<\/strong> are obstacles\u2014technical, psychological, informational, or process-related\u2014that reduce the likelihood a user will convert at a specific step. They can be obvious (a broken checkout button) or subtle (unclear value proposition, missing trust signals, or a form that feels \u201ctoo invasive\u201d).<\/p>\n\n\n\n

The core concept is simple: conversions fail when the perceived effort, risk, or confusion outweighs the perceived value. Business-wise, Conversion Blockers translate directly into wasted ad spend, lower pipeline, lower revenue, and misleading performance assessments.<\/p>\n\n\n\n

In Conversion & Measurement<\/strong>, Conversion Blockers are detected through behavioral data (drop-offs, error rates, time to complete) and qualitative insight (user feedback, session replays, usability testing). In CRO<\/strong>, they become hypotheses: \u201cIf we remove this friction, conversion rate will increase,\u201d then validated through experimentation or structured before\/after analysis.<\/p>\n\n\n\n

Why Conversion Blockers Matters in Conversion & Measurement<\/h2>\n\n\n\n

Conversion Blockers are strategically important because they explain the \u201cwhy\u201d behind performance. Many teams can see that a landing page converts at 1.2%; fewer can prove what is stopping the other 98.8% and what to fix first. Strong Conversion & Measurement<\/strong> turns symptoms into diagnoses.<\/p>\n\n\n\n

Business value typically shows up in a few measurable outcomes:<\/p>\n\n\n\n

    \n
  • More conversions from existing traffic<\/strong>: Fixing Conversion Blockers often improves performance without increasing media budgets.<\/li>\n
  • Lower acquisition costs<\/strong>: When conversion rates rise, the cost per lead or cost per acquisition usually drops.<\/li>\n
  • More accurate forecasting<\/strong>: Reduced funnel volatility improves predictability for revenue teams.<\/li>\n
  • Competitive advantage<\/strong>: In saturated markets, experience and trust become differentiators; removing Conversion Blockers makes buying easier than competitors.<\/li>\n<\/ul>\n\n\n\n

    In CRO<\/strong>, Conversion Blockers also help prioritize effort. Instead of debating opinions, teams focus on the frictions with the strongest data signals and the largest funnel impact.<\/p>\n\n\n\n

    How Conversion Blockers Works (In Practice)<\/h2>\n\n\n\n

    Conversion Blockers are more of a diagnostic concept than a single workflow, but in practice they follow a consistent loop within Conversion & Measurement<\/strong> and CRO<\/strong>:<\/p>\n\n\n\n

      \n
    1. \n

      Trigger: performance signal or stakeholder question<\/strong>\n Examples include a sudden conversion drop, high bounce rate from a campaign, a checkout step with unusual abandonment, or low lead quality.<\/p>\n<\/li>\n

    2. \n

      Analysis: identify where and why users get stuck<\/strong>\n Teams use funnel reports, event data, error logs, heatmaps, and voice-of-customer inputs to isolate the step and the friction. This is where measurement design matters: you can\u2019t find Conversion Blockers you aren\u2019t tracking.<\/p>\n<\/li>\n

    3. \n

      Application: remove friction or reduce risk<\/strong>\n Fixes might be UX copy changes, performance improvements, reducing form fields, improving trust cues, clarifying pricing, or simplifying navigation. In CRO<\/strong>, these are translated into testable hypotheses or iterative improvements.<\/p>\n<\/li>\n

    4. \n

      Outcome: validate impact and monitor stability<\/strong>\n Improvements are confirmed through experimentation (A\/B testing) or careful pre\/post comparisons with guardrails. In Conversion & Measurement<\/strong>, you also monitor downstream metrics like refund rate, churn, lead qualification rate, and support tickets to ensure you didn\u2019t \u201coptimize\u201d into lower quality.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

      Key Components of Conversion Blockers<\/h2>\n\n\n\n

      Conversion Blockers span disciplines, so the components are a mix of data, process, and ownership:<\/p>\n\n\n\n

      Data inputs and instrumentation<\/h3>\n\n\n\n

      Good Conversion & Measurement<\/strong> requires event tracking for key steps: view content, click CTA, start form, submit form, add to cart, begin checkout, payment success, and error events. Without this, Conversion Blockers hide behind \u201coverall conversion rate.\u201d<\/p>\n\n\n\n

      Diagnostic processes<\/h3>\n\n\n\n

      Common processes include funnel analysis, segmentation (device, channel, geography, returning vs new), usability reviews, and structured audits of landing pages and checkout flows. In CRO<\/strong>, teams often maintain a backlog of suspected Conversion Blockers with evidence and prioritization scores.<\/p>\n\n\n\n

      Team responsibilities and governance<\/h3>\n\n\n\n

      Ownership is crucial: marketing can fix messaging, product can fix flows, engineering can fix performance and bugs, analytics can fix measurement gaps. A clear escalation path reduces the time a Conversion Blocker remains live.<\/p>\n\n\n\n

      Systems and feedback loops<\/h3>\n\n\n\n

      Support tickets, chat logs, call center notes, NPS comments, and on-site surveys often reveal Conversion Blockers that analytics alone can\u2019t explain (e.g., \u201cI don\u2019t trust this,\u201d \u201cI can\u2019t find shipping info,\u201d \u201cCoupon didn\u2019t work\u201d).<\/p>\n\n\n\n

      Types of Conversion Blockers<\/h2>\n\n\n\n

      There aren\u2019t universal formal \u201ctypes,\u201d but these categories are practical for CRO<\/strong> and Conversion & Measurement<\/strong> work:<\/p>\n\n\n\n

      Technical blockers<\/h3>\n\n\n\n

      Issues that prevent completion: broken links, 404s, JavaScript errors, payment failures, slow pages, mobile layout bugs, or inaccessible forms. These often create sharp drop-offs in funnel step reports.<\/p>\n\n\n\n

      UX and usability blockers<\/h3>\n\n\n\n

      Users can\u2019t figure out what to do: unclear CTA, confusing navigation, poor contrast, overly long forms, or distracting pop-ups. These tend to increase time-on-step, rage clicks, and abandonment.<\/p>\n\n\n\n

      Trust and risk blockers<\/h3>\n\n\n\n

      Users hesitate due to perceived risk: unclear returns, missing contact info, weak social proof, confusing pricing, surprise fees, or unclear security\/payment messaging. These show up especially in checkout and lead-gen steps.<\/p>\n\n\n\n

      Relevance and message-match blockers<\/h3>\n\n\n\n

      A campaign promises one thing and the landing page delivers another. In Conversion & Measurement<\/strong>, you\u2019ll see high clicks but low engagement and quick exits from specific channels or ad groups.<\/p>\n\n\n\n

      Process and policy blockers<\/h3>\n\n\n\n

      Operational constraints: mandatory account creation, limited payment options, restrictive shipping policies, or lead forms that require information users can\u2019t reasonably provide.<\/p>\n\n\n\n

      Real-World Examples of Conversion Blockers<\/h2>\n\n\n\n

      Example 1: Paid campaign to a lead form that \u201clooks spammy\u201d<\/h3>\n\n\n\n

      A B2B SaaS runs a high-intent search campaign. Click-through rate is strong, but form submissions are low. Conversion & Measurement<\/strong> shows many users start the form and abandon at the phone number field. Session replays show hesitation and backtracking.<\/p>\n\n\n\n

      CRO<\/strong> fix: make the phone number optional, add a short privacy note, and clarify response time. Outcome: form completion increases, and lead quality remains stable because the sales team still captures phone numbers later when appropriate.<\/p>\n\n\n\n

      Example 2: Ecommerce checkout drop caused by unexpected costs<\/h3>\n\n\n\n

      An ecommerce site has steady add-to-cart rates but high checkout abandonment at shipping. Funnel reporting in Conversion & Measurement<\/strong> shows a sharp drop when shipping is first revealed. Customer feedback mentions \u201csurprise fees.\u201d<\/p>\n\n\n\n

      CRO<\/strong> fix: show estimated shipping earlier, simplify delivery options, and clarify returns. Outcome: fewer late-stage exits, improved conversion rate, and reduced \u201cprice shock\u201d support contacts.<\/p>\n\n\n\n

      Example 3: Mobile performance undermining organic traffic<\/h3>\n\n\n\n

      A content-led brand ranks well and gets strong mobile organic traffic, but conversions lag. In Conversion & Measurement<\/strong>, mobile users have a higher bounce rate and lower CTA clicks; performance data indicates long load times on mobile.<\/p>\n\n\n\n

      CRO<\/strong> fix: optimize images, reduce script weight, and improve Core Web Vitals. Outcome: faster loads, higher engagement, and more email sign-ups from SEO traffic\u2014without changing the offer.<\/p>\n\n\n\n

      Benefits of Using Conversion Blockers (As a Diagnostic Lens)<\/h2>\n\n\n\n

      Treating Conversion Blockers as a structured practice delivers practical gains:<\/p>\n\n\n\n

        \n
      • Performance improvements<\/strong>: Higher conversion rates at key steps\u2014checkout, forms, trials, and sign-ups.<\/li>\n
      • Cost savings<\/strong>: Better conversion efficiency lowers paid media costs and reduces wasted spend on traffic that can\u2019t convert.<\/li>\n
      • Operational efficiency<\/strong>: Fewer support tickets and fewer \u201cmystery\u201d performance issues when measurement pinpoints the root cause.<\/li>\n
      • Better customer experience<\/strong>: Less friction, more clarity, and fewer unpleasant surprises improve trust and long-term loyalty.<\/li>\n<\/ul>\n\n\n\n

        In Conversion & Measurement<\/strong>, these benefits compound because each fix improves data quality and reduces noise in your funnels.<\/p>\n\n\n\n

        Challenges of Conversion Blockers<\/h2>\n\n\n\n

        Conversion Blockers can be straightforward to spot but difficult to resolve well:<\/p>\n\n\n\n

          \n
        • Measurement limitations<\/strong>: Privacy changes, consent requirements, and tracking gaps can hide where friction occurs. In Conversion & Measurement<\/strong>, missing events can mimic user drop-off.<\/li>\n
        • Attribution confusion<\/strong>: Teams may blame channels when the real issue is an on-site Conversion Blocker. This leads to budget shifts instead of fixes.<\/li>\n
        • Local maxima in CRO<\/strong>: Over-optimizing for conversion rate can reduce lead quality, increase returns, or harm brand trust. You need guardrail metrics.<\/li>\n
        • Cross-team dependencies<\/strong>: Many Conversion Blockers require engineering time, policy changes, or legal approval, slowing execution.<\/li>\n
        • Segment-specific friction<\/strong>: A flow might work for desktop users but fail on certain mobile devices, browsers, languages, or payment methods.<\/li>\n<\/ul>\n\n\n\n

          Best Practices for Conversion Blockers<\/h2>\n\n\n\n

          Start with the funnel, then segment<\/h3>\n\n\n\n

          Use Conversion & Measurement<\/strong> to map the exact steps to conversion and identify the largest drop-offs. Then segment by channel, device, geography, new vs returning, and landing page. Conversion Blockers are often concentrated in one segment.<\/p>\n\n\n\n

          Combine quantitative and qualitative evidence<\/h3>\n\n\n\n

          Pair funnel analytics with session replays, heatmaps, on-site surveys, usability testing, and support feedback. CRO<\/strong> hypotheses are stronger when they explain both the numbers and the user experience.<\/p>\n\n\n\n

          Prioritize by impact and effort<\/h3>\n\n\n\n

          A useful prioritization approach considers:\n– Potential conversion lift (size of affected audience \u00d7 severity of drop-off)\n– Confidence (strength of evidence)\n– Effort (engineering\/design complexity)<\/p>\n\n\n\n

          Fix measurement before testing<\/h3>\n\n\n\n

          If you can\u2019t reliably measure the step, you can\u2019t confirm the Conversion Blocker or the improvement. Ensure event naming, deduplication, and consent behavior are consistent in your Conversion & Measurement<\/strong> setup.<\/p>\n\n\n\n

          Use guardrails to avoid \u201cbad wins\u201d<\/h3>\n\n\n\n

          Track downstream outcomes such as lead qualification rate, refund rate, churn, chargebacks, or support tickets. In CRO<\/strong>, a lift that harms quality is not a real win.<\/p>\n\n\n\n

          Document learnings and standardize patterns<\/h3>\n\n\n\n

          When you remove recurring Conversion Blockers (like unclear pricing or excessive form fields), turn the solution into a template or guideline so new pages don\u2019t reintroduce the same friction.<\/p>\n\n\n\n

          Tools Used for Conversion Blockers<\/h2>\n\n\n\n

          Conversion Blockers are discovered and managed through categories of tools rather than one \u201cblocker tool\u201d:<\/p>\n\n\n\n

            \n
          • Analytics tools<\/strong>: Funnel analysis, event tracking, segmentation, cohort analysis, and path exploration to identify where drop-offs occur in Conversion & Measurement<\/strong>.<\/li>\n
          • Tag management and instrumentation<\/strong>: Governance over events, triggers, consent behavior, and version control to keep measurement reliable.<\/li>\n
          • Experimentation and personalization platforms<\/strong>: A\/B testing, multivariate testing, and controlled rollouts used in CRO<\/strong> to validate changes.<\/li>\n
          • User behavior tools<\/strong>: Heatmaps, scroll maps, session replays, and on-site polls that reveal confusion, hesitation, and UI friction.<\/li>\n
          • Performance monitoring<\/strong>: Real user monitoring and error tracking to catch technical Conversion Blockers like slow loads, JS errors, and failed network requests.<\/li>\n
          • CRM and marketing automation<\/strong>: Lead routing, form handling, nurture flows, and lifecycle tracking to ensure \u201cconversion\u201d is connected to actual business outcomes.<\/li>\n
          • Reporting dashboards<\/strong>: Unified views of conversion, quality, and guardrail metrics for ongoing Conversion & Measurement<\/strong> oversight.<\/li>\n<\/ul>\n\n\n\n

            Metrics Related to Conversion Blockers<\/h2>\n\n\n\n

            To manage Conversion Blockers, focus on metrics that reveal friction and its business impact:<\/p>\n\n\n\n

              \n
            • Step conversion rate and step abandonment rate<\/strong> (per funnel stage)<\/li>\n
            • Form start vs form submit rate<\/strong> (and per-field drop-off where available)<\/li>\n
            • Error rate<\/strong> (payment failures, validation errors, 404s, JS errors)<\/li>\n
            • Page speed and interaction metrics<\/strong> (load time, responsiveness, stability)<\/li>\n
            • Rage clicks \/ dead clicks indicators<\/strong> (signals of broken or confusing UI)<\/li>\n
            • Revenue per session \/ lead value metrics<\/strong> (to connect CRO improvements to outcomes)<\/li>\n
            • Cost per acquisition and cost per qualified lead<\/strong> (to quantify efficiency gains)<\/li>\n
            • Refund\/return rate, churn, or cancellation rate<\/strong> (guardrails against low-quality conversions)<\/li>\n<\/ul>\n\n\n\n

              In Conversion & Measurement<\/strong>, the goal is to tie observed friction to both conversion performance and downstream quality.<\/p>\n\n\n\n

              Future Trends of Conversion Blockers<\/h2>\n\n\n\n

              Several shifts are changing how Conversion Blockers are identified and resolved within Conversion & Measurement<\/strong>:<\/p>\n\n\n\n

                \n
              • AI-assisted diagnosis<\/strong>: Automated anomaly detection, clustering of session patterns, and faster summarization of user feedback will shorten time-to-insight.<\/li>\n
              • Privacy-first measurement<\/strong>: Consent-driven tracking, modeled conversions, and aggregated reporting will require better instrumentation design and more reliance on first-party data.<\/li>\n
              • Personalization with constraints<\/strong>: Experience tailoring can reduce Conversion Blockers (e.g., showing relevant proof points), but it must be balanced with transparency and measurement rigor.<\/li>\n
              • Rising performance expectations<\/strong>: Mobile experience and speed will remain central; technical Conversion Blockers will be less tolerated as competitors optimize.<\/li>\n
              • More end-to-end optimization<\/strong>: CRO<\/strong> will increasingly connect on-site improvements to lifecycle outcomes (activation, retention, expansion), not just first conversion.<\/li>\n<\/ul>\n\n\n\n

                Conversion Blockers vs Related Terms<\/h2>\n\n\n\n

                Conversion Blockers vs friction<\/h3>\n\n\n\n

                \u201cFriction\u201d is the broader idea of any effort in a user journey. Conversion Blockers<\/strong> are friction points that materially prevent or significantly reduce conversion\u2014often measurable as drop-offs or failures in Conversion & Measurement<\/strong>.<\/p>\n\n\n\n

                Conversion Blockers vs drop-off points<\/h3>\n\n\n\n

                A drop-off point is a location in the funnel where users leave. A Conversion Blocker is the reason<\/em> for that drop-off. CRO<\/strong> work connects the two: where users leave and why.<\/p>\n\n\n\n

                Conversion Blockers vs objections<\/h3>\n\n\n\n

                Objections are reasons users hesitate (price, trust, need, timing). They can be Conversion Blockers when the page or flow fails to address them\u2014such as missing return policies, unclear pricing, or lack of proof.<\/p>\n\n\n\n

                Who Should Learn Conversion Blockers<\/h2>\n\n\n\n
                  \n
                • Marketers<\/strong> benefit by improving landing pages, campaign alignment, and lead generation efficiency with better Conversion & Measurement<\/strong> insight.<\/li>\n
                • Analysts<\/strong> gain a framework to translate funnel anomalies into actionable diagnoses and better measurement design.<\/li>\n
                • Agencies<\/strong> can deliver more value by pairing acquisition with CRO<\/strong> improvements, reducing client churn caused by \u201ctraffic with no results.\u201d<\/li>\n
                • Business owners and founders<\/strong> can prioritize changes that unlock revenue without constantly increasing spend.<\/li>\n
                • Developers<\/strong> can focus technical work on high-impact failures: performance, errors, accessibility, and reliability\u2014often the most severe Conversion Blockers.<\/li>\n<\/ul>\n\n\n\n

                  Summary of Conversion Blockers<\/h2>\n\n\n\n

                  Conversion Blockers<\/strong> are the obstacles that stop users from completing key actions. They matter because they turn \u201cgood traffic\u201d into real outcomes, reduce wasted spend, and improve customer experience. In Conversion & Measurement<\/strong>, they are discovered through funnel tracking, segmentation, and feedback signals. In CRO<\/strong>, they become prioritized hypotheses and fixes\u2014validated with careful testing and guarded by downstream quality metrics.<\/p>\n\n\n\n

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

                  1) What are Conversion Blockers, in simple terms?<\/h3>\n\n\n\n

                  Conversion Blockers are the problems that prevent a user from completing a desired action, such as a purchase or form submission. They can be technical (errors), experiential (confusing UI), or psychological (lack of trust).<\/p>\n\n\n\n

                  2) How do I find Conversion Blockers if my tracking isn\u2019t perfect?<\/h3>\n\n\n\n

                  Start with what you can measure in Conversion & Measurement<\/strong> (step drop-offs, device differences, error logs), then add qualitative inputs like session replays, on-site surveys, and support feedback. Also prioritize fixing instrumentation so future analysis is reliable.<\/p>\n\n\n\n

                  3) Are Conversion Blockers always on the website?<\/h3>\n\n\n\n

                  No. They can exist in policies (returns, shipping), operational processes (slow follow-up, broken lead routing), or even in message mismatch between ads and landing pages. The blocker is wherever the user decides \u201cthis is too hard\/risky\/unclear.\u201d<\/p>\n\n\n\n

                  4) How does CRO address Conversion Blockers without hurting lead quality?<\/h3>\n\n\n\n

                  Good CRO<\/strong> uses guardrail metrics\u2014lead qualification rate, churn, refunds, or downstream revenue\u2014so improvements don\u2019t just increase volume, but maintain or improve quality.<\/p>\n\n\n\n

                  5) What\u2019s the fastest Conversion Blocker to fix with high impact?<\/h3>\n\n\n\n

                  Technical issues (broken buttons, form errors, payment failures) and page speed problems often create immediate gains. They\u2019re also easier to validate in Conversion & Measurement<\/strong> because the before\/after change is clear.<\/p>\n\n\n\n

                  6) Should I A\/B test every change aimed at Conversion Blockers?<\/h3>\n\n\n\n

                  Not always. Severe technical Conversion Blockers should be fixed immediately. For messaging, layout, and persuasion changes, CRO<\/strong> testing is usually worthwhile\u2014especially when you\u2019re trading off clarity, trust, and brand perception.<\/p>\n\n\n\n

                  7) How often should teams review Conversion Blockers?<\/h3>\n\n\n\n

                  At minimum monthly, and weekly for high-traffic funnels (paid landing pages, checkout, core lead forms). Many teams set alerts in Conversion & Measurement<\/strong> to flag sudden conversion drops or spikes in errors that indicate new Conversion Blockers.<\/p>\n","protected":false},"excerpt":{"rendered":"

                  Conversion Blockers are anything that prevents a user from completing a desired action\u2014buying, subscribing, requesting a demo, downloading a resource, or even progressing to the next step in a funnel. In **Conversion & Measurement**, they show up as unexplained drop-offs, poor form completion, rising acquisition costs, or \u201cgood traffic\u201d that doesn\u2019t turn into outcomes. In **CRO**, they are the friction points you identify, prioritize, and remove to unlock more revenue from the same demand.<\/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":[1889],"tags":[],"class_list":["post-7125","post","type-post","status-publish","format-standard","hentry","category-cro"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/7125","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=7125"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/7125\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=7125"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=7125"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=7125"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}