{"id":7247,"date":"2026-03-24T05:38:03","date_gmt":"2026-03-24T05:38:03","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/cro-testing-framework\/"},"modified":"2026-03-24T05:38:03","modified_gmt":"2026-03-24T05:38:03","slug":"cro-testing-framework","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/cro-testing-framework\/","title":{"rendered":"CRO Testing Framework: What It Is, Key Features, Benefits, Use Cases, and How It Fits in CRO"},"content":{"rendered":"\n

A CRO Testing Framework<\/strong> is a structured way to plan, run, measure, and learn from experiments that improve conversions. In Conversion & Measurement<\/strong>, it acts like a quality system: it reduces guesswork, standardizes how teams evaluate evidence, and makes outcomes repeatable. In CRO<\/strong>, where small UX and messaging changes can meaningfully affect revenue, a framework ensures those changes are tested responsibly\u2014using reliable data, clear hypotheses, and consistent decision rules.<\/p>\n\n\n\n

A strong CRO Testing Framework<\/strong> matters because modern marketing is complex: multiple channels drive users to multiple experiences across devices, and measurement is constrained by privacy, consent, and tracking limitations. Without a framework, teams often ship \u201coptimizations\u201d that are really opinions, misread noisy results, or waste traffic on low-impact tests. With a framework, Conversion & Measurement<\/strong> becomes a continuous learning system that compounds over time.<\/p>\n\n\n\n

What Is CRO Testing Framework?<\/h2>\n\n\n\n

A CRO Testing Framework<\/strong> is a documented process and set of standards for running experiments designed to increase conversions (purchases, sign-ups, leads, or any defined business action). It defines:<\/p>\n\n\n\n

    \n
  • How to choose what to test <\/li>\n
  • How to design the test (hypothesis, variants, success metrics) <\/li>\n
  • How to run it (targeting, QA, instrumentation) <\/li>\n
  • How to analyze and decide (validity checks, significance, practical impact) <\/li>\n
  • How to operationalize learning (rollouts, documentation, next steps)<\/li>\n<\/ul>\n\n\n\n

    The core concept is simple: treat optimization as an evidence-driven workflow rather than a series of ad hoc changes. Business-wise, a CRO Testing Framework<\/strong> protects revenue by reducing the risk of shipping harmful changes, and it improves profitability by focusing effort on the highest expected impact.<\/p>\n\n\n\n

    In Conversion & Measurement<\/strong>, the framework is the bridge between user behavior data and business decisions. Inside CRO<\/strong>, it becomes the operating system for experimentation\u2014especially when multiple teams (product, design, marketing, analytics, engineering) share responsibility.<\/p>\n\n\n\n

    Why CRO Testing Framework Matters in Conversion & Measurement<\/h2>\n\n\n\n

    A CRO Testing Framework<\/strong> improves strategic clarity in Conversion & Measurement<\/strong> by aligning everyone on what \u201csuccess\u201d means, how it will be measured, and how decisions will be made. That alignment prevents common problems like optimizing for the wrong metric (e.g., clicks instead of qualified leads) or celebrating short-term lifts that don\u2019t translate to revenue.<\/p>\n\n\n\n

    Business value typically shows up in four ways:<\/p>\n\n\n\n

      \n
    • Higher conversion efficiency:<\/strong> More outcomes from the same traffic and spend. <\/li>\n
    • Reduced opportunity cost:<\/strong> Less time spent on low-impact ideas or inconclusive tests. <\/li>\n
    • Better decision quality:<\/strong> Fewer \u201cfalse wins\u201d caused by noisy data or biased interpretation. <\/li>\n
    • Competitive advantage:<\/strong> Faster learning cycles help you adapt messaging, offers, and UX sooner than competitors.<\/li>\n<\/ul>\n\n\n\n

      In CRO<\/strong>, consistent experimentation also improves stakeholder trust. When leaders see repeatable methods and clean reporting, they fund experimentation programs more confidently.<\/p>\n\n\n\n

      How CRO Testing Framework Works<\/h2>\n\n\n\n

      In practice, a CRO Testing Framework<\/strong> works as a loop that turns data into decisions and decisions into measurable outcomes:<\/p>\n\n\n\n

        \n
      1. \n

        Input \/ Trigger<\/strong>\n Inputs include funnel drop-offs, customer feedback, session recordings, paid campaign performance, SEO landing page engagement, or product analytics insights. In Conversion & Measurement<\/strong>, the trigger should be a measurable problem (e.g., low checkout completion) rather than a vague goal (e.g., \u201cmake it look better\u201d).<\/p>\n<\/li>\n

      2. \n

        Analysis \/ Processing<\/strong>\n Teams diagnose why users fail to convert, using behavioral data (events, funnels), qualitative insights (surveys, user tests), and context (traffic mix, device, geo). The framework forces a clear hypothesis that links cause \u2192 change \u2192 expected impact.<\/p>\n<\/li>\n

      3. \n

        Execution \/ Application<\/strong>\n The test is designed with defined variants, targeting rules, instrumentation, and QA steps. The CRO Testing Framework<\/strong> also defines guardrails: minimum sample size targets, runtime expectations, and what metrics must not degrade (e.g., refund rate, churn, or lead quality).<\/p>\n<\/li>\n

      4. \n

        Output \/ Outcome<\/strong>\n Results are analyzed and translated into a decision: ship, iterate, or stop. Critically, the output is not just \u201cwin\/loss,\u201d but documented learning that improves future tests\u2014an essential part of Conversion & Measurement<\/strong> maturity.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

        Key Components of CRO Testing Framework<\/h2>\n\n\n\n

        A durable CRO Testing Framework<\/strong> typically includes these elements:<\/p>\n\n\n\n

        Strategy and governance<\/h3>\n\n\n\n
          \n
        • Clear conversion goals and a measurement plan tied to business outcomes <\/li>\n
        • Roles and responsibilities (requester, analyst, designer, engineer, approver) <\/li>\n
        • A testing policy (traffic allocation, risk level, approval flow)<\/li>\n<\/ul>\n\n\n\n

          Research and prioritization<\/h3>\n\n\n\n
            \n
          • A standardized intake method for ideas (form or backlog) <\/li>\n
          • A prioritization model that weighs impact, confidence, and effort <\/li>\n
          • A research toolkit (analytics review, heatmaps, surveys, customer calls)<\/li>\n<\/ul>\n\n\n\n

            Experiment design standards<\/h3>\n\n\n\n
              \n
            • Hypothesis template that specifies audience, change, expected behavior shift, and metric <\/li>\n
            • Variant design rules (one core change vs. many changes; accessibility checks) <\/li>\n
            • Guardrail metrics and segmentation plan (new vs. returning, device, channel)<\/li>\n<\/ul>\n\n\n\n

              Measurement and analysis standards<\/h3>\n\n\n\n
                \n
              • Event taxonomy and tracking governance aligned to Conversion & Measurement<\/strong> <\/li>\n
              • QA checklists for instrumentation and data validation <\/li>\n
              • Decision rules (statistical approach, minimum runtime, handling novelty effects)<\/li>\n<\/ul>\n\n\n\n

                Knowledge management<\/h3>\n\n\n\n
                  \n
                • A results repository with context, screenshots, data notes, and decisions <\/li>\n
                • A learning agenda that connects tests to broader customer and product insights <\/li>\n
                • Post-test rollout plan (monitoring after shipping, performance tracking)<\/li>\n<\/ul>\n\n\n\n

                  Types of CRO Testing Framework<\/h2>\n\n\n\n

                  There isn\u2019t one universal \u201cofficial\u201d set of types, but teams commonly use different CRO Testing Framework<\/strong> approaches depending on maturity and risk tolerance:<\/p>\n\n\n\n

                  1) Prioritization-led frameworks<\/h3>\n\n\n\n

                  These emphasize how ideas are scored and selected (impact vs. effort vs. confidence). They\u2019re useful when many stakeholders submit ideas and the bottleneck is choosing the best bets.<\/p>\n\n\n\n

                  2) Research-led frameworks<\/h3>\n\n\n\n

                  These start with structured discovery (analytics + qualitative research) before proposing tests. In CRO<\/strong>, research-led programs often produce fewer tests, but higher win rates and more durable improvements.<\/p>\n\n\n\n

                  3) Experimentation design frameworks<\/h3>\n\n\n\n

                  These focus on test architecture: A\/B tests, multivariate tests, split-URL tests, holdouts, and sequential testing. They help teams avoid invalid comparisons and improve analytical rigor in Conversion & Measurement<\/strong>.<\/p>\n\n\n\n

                  4) Maturity-based frameworks<\/h3>\n\n\n\n

                  Organizations evolve from \u201crandom tests\u201d to \u201cprogrammatic experimentation,\u201d where hypotheses map to customer journey stages and learning themes. A maturity-based CRO Testing Framework<\/strong> often adds stronger governance, automated QA, and cross-channel measurement discipline.<\/p>\n\n\n\n

                  Real-World Examples of CRO Testing Framework<\/h2>\n\n\n\n

                  Example 1: E-commerce checkout drop-off reduction<\/h3>\n\n\n\n

                  A retailer sees high add-to-cart rates but poor checkout completion. Using a CRO Testing Framework<\/strong>, the team:\n– Diagnoses drop-off at shipping step via funnel analysis and session reviews\n– Hypothesizes that surprise costs and form friction reduce completion\n– Tests an \u201call-in pricing\u201d summary earlier in the flow and simplifies address entry\n– Measures checkout completion rate, revenue per visitor, and guardrails like refund rate <\/p>\n\n\n\n

                  Because this is tied to Conversion & Measurement<\/strong>, the team also validates that revenue tracking and attribution are consistent across devices and channels.<\/p>\n\n\n\n

                  Example 2: B2B lead quality improvement on a campaign landing page<\/h3>\n\n\n\n

                  A SaaS company wants more demo requests but also better-fit leads. The CRO Testing Framework<\/strong> requires:\n– Clear primary metric (qualified demo rate), not just form submits\n– A test that reframes the value proposition and adds a short qualification step\n– Guardrails like sales-accepted lead rate and pipeline conversion <\/p>\n\n\n\n

                  This is classic CRO<\/strong>: optimizing not only volume, but downstream quality to protect sales efficiency.<\/p>\n\n\n\n

                  Example 3: Content-to-newsletter conversion for a publisher<\/h3>\n\n\n\n

                  A publisher improves on-page subscription growth by:\n– Segmenting traffic by source (search vs. social) in Conversion & Measurement<\/strong>\n– Testing different newsletter CTAs based on article category and user depth\n– Tracking long-term engagement (opens, retention) to avoid short-term wins that churn <\/p>\n\n\n\n

                  A CRO Testing Framework<\/strong> helps ensure tests don\u2019t degrade page performance or user experience.<\/p>\n\n\n\n

                  Benefits of Using CRO Testing Framework<\/h2>\n\n\n\n

                  A well-run CRO Testing Framework<\/strong> delivers benefits beyond \u201chigher conversion rate\u201d:<\/p>\n\n\n\n

                    \n
                  • Performance improvements:<\/strong> Higher revenue per visitor, lead yield, or activation rate through disciplined experimentation. <\/li>\n
                  • Cost savings:<\/strong> Better conversion efficiency lowers acquisition costs by extracting more value from existing traffic. <\/li>\n
                  • Operational efficiency:<\/strong> Shared templates, QA steps, and decision rules reduce rework and stakeholder debates. <\/li>\n
                  • Customer experience gains:<\/strong> Tests grounded in user problems often reduce friction, increase trust, and improve accessibility. <\/li>\n
                  • Better learning:<\/strong> Even inconclusive tests become useful when insights are documented and reused\u2014central to Conversion & Measurement<\/strong> excellence.<\/li>\n<\/ul>\n\n\n\n

                    Challenges of CRO Testing Framework<\/h2>\n\n\n\n

                    A CRO Testing Framework<\/strong> also comes with real constraints that teams must manage:<\/p>\n\n\n\n

                      \n
                    • Insufficient sample size:<\/strong> Low-traffic pages can\u2019t support frequent tests without long runtimes. <\/li>\n
                    • Measurement limitations:<\/strong> Consent requirements, cross-device behavior, and tracking gaps can bias results in Conversion & Measurement<\/strong>. <\/li>\n
                    • Confounding variables:<\/strong> Promotions, seasonality, channel mix shifts, and product releases can contaminate experiments. <\/li>\n
                    • Organizational friction:<\/strong> Stakeholders may push for pet ideas, rush timelines, or resist \u201cno change\u201d outcomes. <\/li>\n
                    • Over-optimization risk:<\/strong> In CRO<\/strong>, chasing small uplifts can harm brand clarity or user trust if the framework lacks guardrails.<\/li>\n<\/ul>\n\n\n\n

                      Best Practices for CRO Testing Framework<\/h2>\n\n\n\n

                      To make a CRO Testing Framework<\/strong> reliable and scalable:<\/p>\n\n\n\n

                        \n
                      • Start with a crisp hypothesis:<\/strong> Tie the proposed change to a specific user problem and expected behavior shift. <\/li>\n
                      • Define one primary metric plus guardrails:<\/strong> In Conversion & Measurement<\/strong>, clarity beats complexity. <\/li>\n
                      • Prioritize by expected value, not excitement:<\/strong> Use a consistent scoring approach and revisit it quarterly. <\/li>\n
                      • Run rigorous QA:<\/strong> Verify targeting, variant rendering, performance impact, and event firing before ramping traffic. <\/li>\n
                      • Avoid overlapping tests on the same users:<\/strong> Interference makes results hard to interpret in CRO<\/strong>. <\/li>\n
                      • Segment thoughtfully:<\/strong> Check results by device, channel, and user type\u2014but avoid \u201cfinding significance\u201d by slicing endlessly. <\/li>\n
                      • Document decisions and learning:<\/strong> A results library prevents repeated mistakes and helps onboard new team members. <\/li>\n
                      • Scale gradually:<\/strong> Increase test velocity only when instrumentation, analysis capacity, and governance are stable.<\/li>\n<\/ul>\n\n\n\n

                        Tools Used for CRO Testing Framework<\/h2>\n\n\n\n

                        A CRO Testing Framework<\/strong> is tool-enabled, but not tool-dependent. Common tool categories include:<\/p>\n\n\n\n

                          \n
                        • Analytics tools:<\/strong> Event tracking, funnels, cohorts, and path analysis to support Conversion & Measurement<\/strong> diagnostics. <\/li>\n
                        • Experimentation platforms:<\/strong> A\/B and split testing capabilities, audience targeting, and statistical reporting. <\/li>\n
                        • Tag management and data layer systems:<\/strong> Consistent event definitions and controlled deployment of tracking changes. <\/li>\n
                        • User research tools:<\/strong> Heatmaps, scroll maps, session recordings, surveys, and usability testing to explain \u201cwhy.\u201d <\/li>\n
                        • Reporting dashboards and BI:<\/strong> Shared views of test performance, revenue impact, and guardrail metrics. <\/li>\n
                        • CRM and marketing automation:<\/strong> Lead quality, lifecycle tracking, and downstream outcomes essential to serious CRO<\/strong> decisions. <\/li>\n
                        • SEO and content tools:<\/strong> Landing page performance insights, query intent signals, and content engagement patterns that inform test ideas.<\/li>\n<\/ul>\n\n\n\n

                          Metrics Related to CRO Testing Framework<\/h2>\n\n\n\n

                          A strong CRO Testing Framework<\/strong> defines metrics across the funnel and across time:<\/p>\n\n\n\n

                          Core conversion metrics<\/h3>\n\n\n\n
                            \n
                          • Conversion rate (by step and overall) <\/li>\n
                          • Revenue per visitor \/ average order value (for commerce) <\/li>\n
                          • Lead submit rate and qualified lead rate (for B2B) <\/li>\n
                          • Activation rate (for product-led funnels)<\/li>\n<\/ul>\n\n\n\n

                            Measurement quality metrics (often overlooked)<\/h3>\n\n\n\n
                              \n
                            • Event coverage and tracking error rates <\/li>\n
                            • Share of traffic eligible for testing (consent\/targeting constraints) <\/li>\n
                            • Data latency and reporting consistency across systems in Conversion & Measurement<\/strong><\/li>\n<\/ul>\n\n\n\n

                              Efficiency and ROI metrics<\/h3>\n\n\n\n
                                \n
                              • Cost per acquisition (blended and by channel) <\/li>\n
                              • Incremental revenue or incremental pipeline attributed to winning tests <\/li>\n
                              • Test velocity (tests run, completed, and shipped per month)<\/li>\n<\/ul>\n\n\n\n

                                Experience and brand guardrails<\/h3>\n\n\n\n
                                  \n
                                • Page speed and core performance indicators <\/li>\n
                                • Bounce\/exit rate changes with context <\/li>\n
                                • Refunds, chargebacks, churn, or complaint rates<\/li>\n<\/ul>\n\n\n\n

                                  Future Trends of CRO Testing Framework<\/h2>\n\n\n\n

                                  A CRO Testing Framework<\/strong> is evolving as the industry changes:<\/p>\n\n\n\n

                                    \n
                                  • AI-assisted research and ideation:<\/strong> Faster synthesis of qualitative feedback and behavioral patterns, with humans validating hypotheses and ethics. <\/li>\n
                                  • Personalization with stronger governance:<\/strong> More dynamic experiences, but with stricter controls to avoid fragmented messaging and unreliable measurement. <\/li>\n
                                  • Privacy-driven measurement shifts:<\/strong> More emphasis on first-party data, modeled conversion signals, and server-side instrumentation within Conversion & Measurement<\/strong>. <\/li>\n
                                  • Server-side and hybrid experimentation:<\/strong> Better performance and reduced flicker, plus more reliable testing in complex app environments. <\/li>\n
                                  • Experimentation beyond webpages:<\/strong> More testing in onboarding flows, pricing pages, in-product prompts, and lifecycle messaging\u2014expanding how CRO<\/strong> teams define \u201cconversion.\u201d<\/li>\n<\/ul>\n\n\n\n

                                    CRO Testing Framework vs Related Terms<\/h2>\n\n\n\n

                                    CRO Testing Framework vs A\/B testing<\/h3>\n\n\n\n

                                    A\/B testing is a method (a type of experiment). A CRO Testing Framework<\/strong> is the broader system that decides what<\/em> to A\/B test, how<\/em> to measure it in Conversion & Measurement<\/strong>, and how<\/em> to operationalize outcomes.<\/p>\n\n\n\n

                                    CRO Testing Framework vs CRO strategy<\/h3>\n\n\n\n

                                    A CRO strategy sets direction (goals, target segments, journey priorities). The CRO Testing Framework<\/strong> is the execution and governance layer that turns that strategy into credible tests and repeatable learning.<\/p>\n\n\n\n

                                    CRO Testing Framework vs experimentation program<\/h3>\n\n\n\n

                                    An experimentation program is the organizational initiative (people, cadence, roadmap). A CRO Testing Framework<\/strong> is the playbook that keeps the program consistent and analytically sound.<\/p>\n\n\n\n

                                    Who Should Learn CRO Testing Framework<\/h2>\n\n\n\n
                                      \n
                                    • Marketers:<\/strong> To improve landing pages, offers, and messaging with measurable proof inside Conversion & Measurement<\/strong>. <\/li>\n
                                    • Analysts:<\/strong> To standardize metrics, reduce false positives, and improve decision quality across CRO<\/strong> experiments. <\/li>\n
                                    • Agencies:<\/strong> To deliver repeatable optimization services and communicate results credibly to clients. <\/li>\n
                                    • Business owners and founders:<\/strong> To invest in growth changes that are evidence-backed, not opinion-driven. <\/li>\n
                                    • Developers and product teams:<\/strong> To build testable experiences, maintain clean instrumentation, and support reliable experimentation at scale.<\/li>\n<\/ul>\n\n\n\n

                                      Summary of CRO Testing Framework<\/h2>\n\n\n\n

                                      A CRO Testing Framework<\/strong> is a structured, documented approach to experimentation that improves conversions while protecting measurement integrity. It matters because Conversion & Measurement<\/strong> is only as good as the process that turns data into decisions. By standardizing research, prioritization, experiment design, analysis, and knowledge-sharing, the framework strengthens CRO<\/strong> outcomes and helps organizations learn faster with less risk.<\/p>\n\n\n\n

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

                                      1) What is a CRO Testing Framework used for?<\/h3>\n\n\n\n

                                      It\u2019s used to consistently choose, run, measure, and learn from conversion experiments\u2014so optimization decisions are based on evidence and can be repeated reliably across teams.<\/p>\n\n\n\n

                                      2) How do I build a CRO Testing Framework from scratch?<\/h3>\n\n\n\n

                                      Start with a hypothesis template, a simple prioritization method, a measurement plan (primary metric + guardrails), QA steps for tracking, and a results repository. Then add governance and deeper analytics standards as you mature.<\/p>\n\n\n\n

                                      3) What\u2019s the difference between CRO and Conversion & Measurement?<\/h3>\n\n\n\n

                                      CRO<\/strong> focuses on improving conversion outcomes through changes to experiences and messaging. Conversion & Measurement<\/strong> is the discipline of instrumenting, tracking, validating, and interpreting the data that proves whether those changes worked.<\/p>\n\n\n\n

                                      4) How many metrics should each test have?<\/h3>\n\n\n\n

                                      Ideally one primary success metric and a small set of guardrails (often 2\u20135). Too many success metrics increases confusion and makes decision-making less consistent.<\/p>\n\n\n\n

                                      5) Why do many tests come back \u201cinconclusive\u201d?<\/h3>\n\n\n\n

                                      Common causes include low sample size, short runtimes, overlapping tests, noisy traffic, or tracking gaps. A CRO Testing Framework<\/strong> reduces inconclusives by setting minimum requirements and stronger QA.<\/p>\n\n\n\n

                                      6) Should I prioritize more tests or better tests?<\/h3>\n\n\n\n

                                      Early on, prioritize better tests backed by research and clean measurement. As your process stabilizes, you can increase test velocity without sacrificing rigor in Conversion & Measurement<\/strong>.<\/p>\n\n\n\n

                                      7) Can a CRO Testing Framework work for mobile apps and product onboarding?<\/h3>\n\n\n\n

                                      Yes. The same principles apply\u2014clear hypotheses, controlled exposure, strong instrumentation, and guardrails\u2014though implementation often relies more on product analytics events and server-side experimentation patterns.<\/p>\n","protected":false},"excerpt":{"rendered":"

                                      A **CRO Testing Framework** is a structured way to plan, run, measure, and learn from experiments that improve conversions. In **Conversion & Measurement**, it acts like a quality system: it reduces guesswork, standardizes how teams evaluate evidence, and makes outcomes repeatable. In **CRO**, where small UX and messaging changes can meaningfully affect revenue, a framework ensures those changes are tested responsibly\u2014using reliable data, clear hypotheses, and consistent decision rules.<\/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-7247","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\/7247","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=7247"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/7247\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=7247"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=7247"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=7247"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}