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

A CRO Audit<\/strong> is a structured review of your website, landing pages, funnels, and measurement setup to uncover why visitors do (or don\u2019t) convert\u2014and what to improve first. In Conversion & Measurement<\/strong>, it acts as the bridge between \u201cwe have data\u201d and \u201cwe know what to do next.\u201d In CRO<\/strong>, it\u2019s the diagnostic step that prevents teams from guessing, running random tests, or optimizing the wrong parts of the journey.<\/p>\n\n\n\n

Modern marketing stacks create plenty of signals (ads, analytics, CRM, experiments), but they also create blind spots: broken tracking, misleading dashboards, inconsistent definitions, and friction points that never show up in topline metrics. A well-run CRO Audit<\/strong> turns those issues into a prioritized action plan that improves conversion performance with less waste.<\/p>\n\n\n\n

What Is CRO Audit?<\/h2>\n\n\n\n

A CRO Audit<\/strong> is an end-to-end evaluation of your conversion experience and the systems that measure it. For beginners, the simplest definition is: a methodical checkup of what users experience and what your data says, aimed at increasing conversions<\/strong>.<\/p>\n\n\n\n

The core concept is evidence-based optimization. Instead of making changes because they \u201cfeel right,\u201d a CRO Audit<\/strong> identifies constraints and opportunities using a mix of quantitative and qualitative inputs\u2014analytics, user behavior, UX review, copy assessment, funnel diagnostics, and tracking validation.<\/p>\n\n\n\n

From a business perspective, a CRO Audit<\/strong> answers questions decision-makers care about:<\/p>\n\n\n\n

    \n
  • Where are we losing qualified users, and why?<\/li>\n
  • Which pages or steps have the highest revenue impact?<\/li>\n
  • Are we measuring conversions accurately in Conversion & Measurement<\/strong>?<\/li>\n
  • What should we fix now versus test later as part of CRO<\/strong>?<\/li>\n<\/ul>\n\n\n\n

    Within Conversion & Measurement<\/strong>, it ensures that conversion metrics are trustworthy and interpretable. Within CRO<\/strong>, it provides the baseline insights and hypotheses that guide prioritization, experimentation, and rollout.<\/p>\n\n\n\n

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

    A CRO Audit<\/strong> matters because conversion problems are rarely caused by one issue. They\u2019re typically a combination of friction (UX), mismatch (message vs intent), trust gaps, technical performance, and measurement errors. In Conversion & Measurement<\/strong>, even a small tracking gap can mislead budgets, channel strategy, and product decisions.<\/p>\n\n\n\n

    Strategically, a CRO Audit<\/strong> helps you:<\/p>\n\n\n\n

      \n
    • Focus resources on high-impact bottlenecks rather than surface-level tweaks.<\/li>\n
    • Reduce the risk of \u201coptimizing\u201d based on inaccurate or incomplete data.<\/li>\n
    • Align teams on one definition of conversion success (leads, trials, purchases, qualified pipeline).<\/li>\n
    • Build a durable CRO<\/strong> roadmap instead of a collection of one-off fixes.<\/li>\n<\/ul>\n\n\n\n

      The competitive advantage comes from speed and clarity. When your organization can diagnose issues quickly and validate improvements with solid Conversion & Measurement<\/strong>, you iterate faster than competitors who rely on intuition.<\/p>\n\n\n\n

      How CRO Audit Works<\/h2>\n\n\n\n

      A CRO Audit<\/strong> is practical and repeatable. While every business differs, the workflow usually follows four phases:<\/p>\n\n\n\n

        \n
      1. \n

        Input \/ Trigger<\/strong>\n – A drop in conversion rate, rising acquisition costs, poor lead quality, or a major site redesign.\n – A desire to scale growth without increasing ad spend.\n – Concerns about tracking accuracy in Conversion & Measurement<\/strong>.<\/p>\n<\/li>\n

      2. \n

        Analysis \/ Processing<\/strong>\n – Review funnel performance by segment (channel, device, new vs returning, geo).\n – Audit key pages for UX, clarity, persuasion, and technical issues.\n – Validate measurement: events, attribution logic, deduplication, and consistency across tools.\n – Gather qualitative insight: session replays, heatmaps, surveys, support tickets, sales notes.<\/p>\n<\/li>\n

      3. \n

        Execution \/ Application<\/strong>\n – Turn findings into hypotheses and prioritized recommendations.\n – Fix \u201cmust-correct\u201d issues first (broken forms, missing events, slow pages, misleading CTAs).\n – Design experiments where uncertainty remains, following your CRO<\/strong> process.<\/p>\n<\/li>\n

      4. \n

        Output \/ Outcome<\/strong>\n – A prioritized action plan (quick wins, mid-effort improvements, longer-term tests).\n – A measurement checklist and governance rules for Conversion & Measurement<\/strong>.\n – A baseline benchmark to evaluate future improvements.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

        A strong CRO Audit<\/strong> doesn\u2019t just point out flaws\u2014it connects problems to user intent, business impact, and measurement confidence.<\/p>\n\n\n\n

        Key Components of CRO Audit<\/h2>\n\n\n\n

        A thorough CRO Audit<\/strong> typically includes these components:<\/p>\n\n\n\n

        Data and measurement review<\/h3>\n\n\n\n
          \n
        • Conversion definitions (macro vs micro conversions)<\/li>\n
        • Event tracking coverage and accuracy<\/li>\n
        • Funnel step consistency across analytics and CRM<\/li>\n
        • Segment analysis (device, channel, landing page, audience type)<\/li>\n<\/ul>\n\n\n\n

          UX and friction assessment<\/h3>\n\n\n\n
            \n
          • Navigation clarity, content hierarchy, and scannability<\/li>\n
          • Form design, error handling, and field requirements<\/li>\n
          • Mobile experience and accessibility basics<\/li>\n
          • Page speed and front-end stability (layout shifts, broken elements)<\/li>\n<\/ul>\n\n\n\n

            Message and persuasion review<\/h3>\n\n\n\n
              \n
            • Offer clarity (what you get, how it works, who it\u2019s for)<\/li>\n
            • Trust signals (reviews, security cues, guarantees, social proof)<\/li>\n
            • Objection handling (pricing clarity, onboarding steps, hidden requirements)<\/li>\n
            • CTA specificity and alignment with intent<\/li>\n<\/ul>\n\n\n\n

              Process and governance<\/h3>\n\n\n\n
                \n
              • Who owns measurement changes in Conversion & Measurement<\/strong><\/li>\n
              • How experimentation is documented and reviewed<\/li>\n
              • Naming conventions for events and campaigns<\/li>\n
              • Release management (preventing tracking breakage after deployments)<\/li>\n<\/ul>\n\n\n\n

                Together, these elements ensure CRO<\/strong> efforts are grounded in reality\u2014not just opinions.<\/p>\n\n\n\n

                Types of CRO Audit<\/h2>\n\n\n\n

                There isn\u2019t one universal taxonomy, but in practice, a CRO Audit<\/strong> is often scoped in a few common ways:<\/p>\n\n\n\n

                1) Page-level audit<\/h3>\n\n\n\n

                Focuses on individual high-traffic pages (landing pages, pricing, checkout, lead forms). This is useful when you know where performance is lagging.<\/p>\n\n\n\n

                2) Funnel or journey audit<\/h3>\n\n\n\n

                Evaluates the entire path from entry to conversion, often across multiple pages and devices. This approach is common in SaaS trials, ecommerce checkouts, and lead-gen flows\u2014where drop-off analysis is central to Conversion & Measurement<\/strong>.<\/p>\n\n\n\n

                3) Measurement-focused audit<\/h3>\n\n\n\n

                Prioritizes tracking accuracy, event design, attribution logic, and data consistency. This is ideal when stakeholders distrust numbers or when CRO<\/strong> decisions are being made from conflicting reports.<\/p>\n\n\n\n

                4) Audience or segment audit<\/h3>\n\n\n\n

                Examines how different segments convert (paid vs organic, brand vs non-brand, mobile vs desktop, new vs returning). It\u2019s especially valuable when topline conversion rates hide segment-level problems.<\/p>\n\n\n\n

                Most teams combine these approaches rather than treating them as separate projects.<\/p>\n\n\n\n

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

                Example 1: Ecommerce checkout drop-off<\/h3>\n\n\n\n

                An online retailer runs a CRO Audit<\/strong> after noticing stable traffic but declining purchases. In Conversion & Measurement<\/strong>, the audit reveals mobile users abandon at the shipping step. Session replays show address autocomplete fails on certain devices, and the form returns unclear errors. Fixing the form, clarifying error messages, and reducing optional fields improves checkout completion\u2014without changing ad spend. The CRO<\/strong> roadmap then tests trust badges and delivery-date messaging.<\/p>\n\n\n\n

                Example 2: B2B lead-gen quality problem<\/h3>\n\n\n\n

                A B2B service company sees plenty of leads but low sales acceptance. A CRO Audit<\/strong> compares landing page copy, form questions, CRM stages, and lead routing. In Conversion & Measurement<\/strong>, it finds leads from certain campaigns are being counted as conversions even when they fail basic qualification checks. The team updates conversion definitions, introduces a \u201cqualified lead\u201d event, and refines the offer to reduce low-intent submissions. CRO<\/strong> efforts shift from \u201cmore leads\u201d to \u201cbetter leads.\u201d<\/p>\n\n\n\n

                Example 3: SaaS free trial activation gap<\/h3>\n\n\n\n

                A SaaS brand increases trials but revenue doesn\u2019t follow. A CRO Audit<\/strong> maps the journey from signup to activation. It identifies a mismatch: the ads promise a quick outcome, but onboarding requires complex setup. The audit recommends simplifying first-run steps and measuring activation milestones more reliably in Conversion & Measurement<\/strong>. The CRO<\/strong> plan then tests onboarding variants and in-app guidance to improve activated trials and downstream paid conversions.<\/p>\n\n\n\n

                Benefits of Using CRO Audit<\/h2>\n\n\n\n

                A well-executed CRO Audit<\/strong> creates benefits that compound over time:<\/p>\n\n\n\n

                  \n
                • Performance improvements:<\/strong> higher conversion rates, better activation, improved checkout completion, stronger lead-to-customer rates.<\/li>\n
                • Cost savings:<\/strong> better efficiency means you can grow without proportionally increasing ad spend or sales headcount.<\/li>\n
                • Operational efficiency:<\/strong> clearer priorities reduce debates and prevent scattered optimization work.<\/li>\n
                • Improved customer experience:<\/strong> fewer frustrations, clearer messaging, and smoother journeys increase trust and satisfaction.<\/li>\n
                • Better decision-making:<\/strong> tighter Conversion & Measurement<\/strong> reduces the risk of chasing misleading metrics.<\/li>\n<\/ul>\n\n\n\n

                  In mature teams, the biggest win is often focus: knowing what not to optimize.<\/p>\n\n\n\n

                  Challenges of CRO Audit<\/h2>\n\n\n\n

                  A CRO Audit<\/strong> can fail\u2014or underdeliver\u2014when these issues aren\u2019t addressed:<\/p>\n\n\n\n

                    \n
                  • Data quality limitations:<\/strong> missing events, inconsistent UTM practices, cookie restrictions, and cross-domain issues can distort Conversion & Measurement<\/strong>.<\/li>\n
                  • Low traffic or long sales cycles:<\/strong> small sample sizes make it harder to separate signal from noise; recommendations must lean more on qualitative evidence and careful segmentation.<\/li>\n
                  • Internal bias:<\/strong> stakeholders may defend existing designs or \u201cpet ideas,\u201d pushing the audit toward confirmation instead of discovery.<\/li>\n
                  • Tool fragmentation:<\/strong> analytics, CRM, ad platforms, and product data may disagree, creating confusion about what \u201cconversion\u201d truly means.<\/li>\n
                  • Implementation constraints:<\/strong> development bandwidth, design systems, and compliance requirements may limit how quickly CRO<\/strong> changes can be shipped.<\/li>\n<\/ul>\n\n\n\n

                    Addressing these challenges upfront makes the audit more actionable and credible.<\/p>\n\n\n\n

                    Best Practices for CRO Audit<\/h2>\n\n\n\n

                    Use these practices to make a CRO Audit<\/strong> consistently useful:<\/p>\n\n\n\n

                      \n
                    1. \n

                      Start with conversion definitions<\/strong>\n – Clearly define macro conversions (purchase, booked call, trial) and micro conversions (add-to-cart, pricing views, demo clicks).\n – Ensure those definitions match reporting in Conversion & Measurement<\/strong> and downstream business outcomes.<\/p>\n<\/li>\n

                    2. \n

                      Segment before you diagnose<\/strong>\n – Always review conversion rate by device, channel, landing page, and user type.\n – Many \u201csitewide\u201d problems are actually isolated to one segment.<\/p>\n<\/li>\n

                    3. \n

                      Prioritize by impact and confidence<\/strong>\n – Favor fixes that address obvious friction and measurement errors first.\n – Use experiments for uncertain changes, and treat tests as part of your CRO<\/strong> governance.<\/p>\n<\/li>\n

                    4. \n

                      Tie every recommendation to evidence<\/strong>\n – Each finding should reference the specific data, behaviors, or user feedback supporting it.\n – Avoid generic advice like \u201cimprove CTA\u201d unless you can state what\u2019s wrong and why.<\/p>\n<\/li>\n

                    5. \n

                      Create an implementation-ready output<\/strong>\n – Provide acceptance criteria (what \u201cfixed\u201d means), tracking requirements, and QA steps.\n – Align owners across marketing, product, design, and engineering.<\/p>\n<\/li>\n

                    6. \n

                      Make it repeatable<\/strong>\n – Run a lighter CRO Audit<\/strong> quarterly (or after major releases) to keep Conversion & Measurement<\/strong> and conversion UX healthy.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

                      Tools Used for CRO Audit<\/h2>\n\n\n\n

                      A CRO Audit<\/strong> is not about buying more tools, but tools help you observe, validate, and prioritize. Common tool categories include:<\/p>\n\n\n\n

                        \n
                      • Analytics tools:<\/strong> track funnels, events, cohorts, and segments; support investigation in Conversion & Measurement<\/strong>.<\/li>\n
                      • Tag management systems:<\/strong> manage tracking pixels, event rules, and deployment workflows.<\/li>\n
                      • Experimentation and personalization platforms:<\/strong> run A\/B tests, multivariate tests, and targeted experiences as part of CRO<\/strong>.<\/li>\n
                      • Session replay and heatmap tools:<\/strong> reveal friction, confusion, rage clicks, and scroll behavior.<\/li>\n
                      • Survey and feedback tools:<\/strong> collect Voice of Customer (VoC) at key moments (exit intent, post-purchase, post-demo).<\/li>\n
                      • CRM systems and marketing automation:<\/strong> connect lead source and on-site behavior to pipeline stages and revenue.<\/li>\n
                      • Performance monitoring tools:<\/strong> identify speed, stability, and front-end errors that impact conversions.<\/li>\n
                      • Reporting dashboards \/ BI:<\/strong> unify metrics and definitions so teams trust Conversion & Measurement<\/strong> outcomes.<\/li>\n<\/ul>\n\n\n\n

                        The best stack is the one your team can govern, maintain, and interpret reliably.<\/p>\n\n\n\n

                        Metrics Related to CRO Audit<\/h2>\n\n\n\n

                        A CRO Audit<\/strong> typically evaluates metrics across four layers:<\/p>\n\n\n\n

                          \n
                        • Conversion metrics:<\/strong> conversion rate, step-to-step funnel conversion, form completion rate, checkout completion rate, activation rate.<\/li>\n
                        • Value metrics:<\/strong> revenue per visitor, average order value, customer lifetime value (when available), lead-to-customer rate.<\/li>\n
                        • Efficiency metrics:<\/strong> cost per acquisition, cost per qualified lead, time-to-convert, sales cycle length (for B2B).<\/li>\n
                        • Engagement and quality indicators:<\/strong> bounce rate (interpreted carefully), scroll depth, repeat visits, product engagement milestones, refund rate or churn (post-conversion quality).<\/li>\n<\/ul>\n\n\n\n

                          Strong Conversion & Measurement<\/strong> also looks at consistency<\/em>: whether the same conversion counts match across analytics, ads, and CRM after deduplication and attribution rules.<\/p>\n\n\n\n

                          Future Trends of CRO Audit<\/h2>\n\n\n\n

                          The CRO Audit<\/strong> process is evolving alongside changes in Conversion & Measurement<\/strong>:<\/p>\n\n\n\n

                            \n
                          • AI-assisted analysis:<\/strong> faster pattern detection in session replays, anomaly detection in funnels, and automated clustering of user feedback. Human judgment remains essential for prioritization and ethics.<\/li>\n
                          • More server-side and first-party measurement:<\/strong> privacy changes and browser restrictions push teams toward more durable tracking approaches and tighter governance.<\/li>\n
                          • Personalization with accountability:<\/strong> more tailored experiences, but with stricter requirements to measure lift and avoid \u201cdark patterns.\u201d<\/li>\n
                          • Experimentation beyond the page:<\/strong> audits increasingly include onboarding flows, in-app messaging, pricing packaging, and lifecycle communications\u2014expanding CRO<\/strong> into product-led growth.<\/li>\n
                          • Measurement resilience:<\/strong> teams will audit not just pages, but their ability to maintain accurate tracking through frequent releases and multi-platform journeys.<\/li>\n<\/ul>\n\n\n\n

                            In short, CRO Audit<\/strong> is becoming as much about measurement integrity as it is about UX improvements.<\/p>\n\n\n\n

                            CRO Audit vs Related Terms<\/h2>\n\n\n\n

                            CRO Audit vs UX Audit<\/h3>\n\n\n\n

                            A UX audit focuses on usability and experience quality\u2014navigation, accessibility, interaction design, and comprehension. A CRO Audit<\/strong> includes UX, but ties findings to conversion outcomes and validates them with Conversion & Measurement<\/strong> data.<\/p>\n\n\n\n

                            CRO Audit vs Analytics Audit<\/h3>\n\n\n\n

                            An analytics audit checks tracking implementation, event design, reporting accuracy, and data governance. A CRO Audit<\/strong> usually incorporates an analytics audit, but goes further by translating insights into conversion hypotheses, page changes, and a CRO<\/strong> roadmap.<\/p>\n\n\n\n

                            CRO Audit vs A\/B Testing<\/h3>\n\n\n\n

                            A\/B testing is a method to validate whether a change causes a measurable improvement. A CRO Audit<\/strong> is the diagnostic and prioritization process that decides what to test or fix<\/em> and ensures measurement can detect real lift.<\/p>\n\n\n\n

                            Who Should Learn CRO Audit<\/h2>\n\n\n\n
                              \n
                            • Marketers<\/strong> benefit by improving campaign landing pages, aligning offers to intent, and proving performance with solid Conversion & Measurement<\/strong>.<\/li>\n
                            • Analysts<\/strong> use CRO Audit<\/strong> methods to connect data patterns to user behavior, reduce reporting confusion, and strengthen causal thinking.<\/li>\n
                            • Agencies<\/strong> can standardize audits to onboard clients faster, build trust, and create retainers anchored in measurable CRO<\/strong> outcomes.<\/li>\n
                            • Business owners and founders<\/strong> gain clarity on where growth is constrained and how to prioritize fixes without wasting budget.<\/li>\n
                            • Developers<\/strong> benefit by understanding how performance, bugs, and implementation details affect conversions\u2014and how to build measurement that survives releases.<\/li>\n<\/ul>\n\n\n\n

                              Summary of CRO Audit<\/h2>\n\n\n\n

                              A CRO Audit<\/strong> is a structured evaluation of your conversion journey and the measurement systems behind it. It matters because it replaces guesswork with evidence, strengthens Conversion & Measurement<\/strong>, and creates a prioritized plan to improve outcomes. As part of CRO<\/strong>, it helps teams focus on the highest-impact friction points, align on reliable metrics, and build an optimization roadmap that scales.<\/p>\n\n\n\n

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

                              1) What is a CRO Audit and what do you get at the end?<\/h3>\n\n\n\n

                              A CRO Audit<\/strong> is a structured review of your funnel, pages, UX, and tracking. The output is typically a prioritized list of issues and recommendations, plus measurement fixes and a roadmap for implementation and testing.<\/p>\n\n\n\n

                              2) How often should you run a CRO Audit?<\/h3>\n\n\n\n

                              Run a full CRO Audit<\/strong> annually or after major redesigns, and lighter audits quarterly\u2014especially if your product, traffic mix, or tracking changes frequently in Conversion & Measurement<\/strong>.<\/p>\n\n\n\n

                              3) Is a CRO Audit only for websites with high traffic?<\/h3>\n\n\n\n

                              No. Lower-traffic sites can still benefit, but the audit should lean more on qualitative evidence (user feedback, session replays, usability review) and prioritize high-confidence fixes over heavy experimentation.<\/p>\n\n\n\n

                              4) What\u2019s the difference between a CRO Audit and an analytics audit?<\/h3>\n\n\n\n

                              An analytics audit focuses on tracking correctness and reporting consistency. A CRO Audit<\/strong> includes measurement validation but also evaluates persuasion, friction, user intent, and prioritization for CRO<\/strong> improvements.<\/p>\n\n\n\n

                              5) How does a CRO Audit support a broader CRO program?<\/h3>\n\n\n\n

                              It provides the baseline: where users drop off, why it happens, what to fix first, and whether Conversion & Measurement<\/strong> can reliably detect improvement. That foundation makes testing and iteration more effective.<\/p>\n\n\n\n

                              6) What should you fix first after a CRO Audit?<\/h3>\n\n\n\n

                              Start with \u201cstop-the-bleeding\u201d issues: broken forms, missing conversion events, severe mobile UX problems, slow pages, misleading CTAs, or steps that create unnecessary friction. Then move to structured experiments for uncertain changes.<\/p>\n","protected":false},"excerpt":{"rendered":"

                              A **CRO Audit** is a structured review of your website, landing pages, funnels, and measurement setup to uncover why visitors do (or don\u2019t) convert\u2014and what to improve first. In **Conversion & Measurement**, it acts as the bridge between \u201cwe have data\u201d and \u201cwe know what to do next.\u201d In **CRO**, it\u2019s the diagnostic step that prevents teams from guessing, running random tests, or optimizing the wrong parts of the journey.<\/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-7219","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\/7219","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=7219"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/7219\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=7219"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=7219"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=7219"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}