{"id":7171,"date":"2026-03-24T02:52:19","date_gmt":"2026-03-24T02:52:19","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/onsite-survey\/"},"modified":"2026-03-24T02:52:19","modified_gmt":"2026-03-24T02:52:19","slug":"onsite-survey","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/onsite-survey\/","title":{"rendered":"Onsite Survey: What It Is, Key Features, Benefits, Use Cases, and How It Fits in CRO"},"content":{"rendered":"\n

An Onsite Survey<\/strong> is one of the most direct ways to understand why<\/em> people behave the way they do on your website\u2014straight from the visitor, in the moment. In Conversion & Measurement<\/strong>, it fills a critical gap that analytics alone can\u2019t: quantitative tools show what happened, while an Onsite Survey helps explain the motivations, confusion, objections, and intent behind the clicks.<\/p>\n\n\n\n

For CRO<\/strong> (conversion rate optimization), an Onsite Survey is often the fastest path to actionable insight. Instead of guessing why a product page underperforms or why checkout abandonment is high, you can collect structured feedback at key points in the journey and use it to prioritize experiments, improve UX, and refine messaging.<\/p>\n\n\n\n

What Is Onsite Survey?<\/h2>\n\n\n\n

An Onsite Survey<\/strong> is a structured set of questions shown to website visitors while they are on the site (or immediately after a key action) to collect feedback about intent, experience, or obstacles. It can be a single-question poll (\u201cWhat stopped you from checking out today?\u201d) or a short multi-question survey that captures richer context.<\/p>\n\n\n\n

The core concept is simple: collect first-party, session-context feedback<\/strong> tied to a page, step, or audience segment. Business-wise, an Onsite Survey turns qualitative opinions into measurable themes you can act on\u2014supporting better product decisions, clearer positioning, and smoother purchase paths.<\/p>\n\n\n\n

In Conversion & Measurement<\/strong>, Onsite Survey data complements behavioral data (events, funnels, heatmaps) by adding explanations and language from real users. In CRO<\/strong>, it becomes a hypothesis engine: it helps you decide what to test<\/em>, what to fix first<\/em>, and how to phrase<\/em> value propositions using customers\u2019 own words.<\/p>\n\n\n\n

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

An Onsite Survey matters because it improves the quality of decisions. Many conversion problems have multiple plausible causes\u2014pricing, trust, usability, mismatch between ad promise and landing page, missing information, or competitor comparisons. Conversion & Measurement<\/strong> teams that rely only on analytics often overfit to patterns without understanding intent.<\/p>\n\n\n\n

Key strategic advantages include:<\/p>\n\n\n\n

    \n
  • Faster root-cause discovery:<\/strong> Identify blockers like shipping surprises, unclear plans, or missing integrations without weeks of speculation.<\/li>\n
  • Higher-quality CRO hypotheses:<\/strong> Convert feedback into testable hypotheses (e.g., \u201cAdd delivery estimate above the fold to reduce uncertainty.\u201d).<\/li>\n
  • Message-market fit validation:<\/strong> Confirm whether visitors understand your offer and why they came.<\/li>\n
  • Competitive edge:<\/strong> Learn what alternatives visitors consider and what they need to choose you, then feed that into landing pages, FAQs, and product copy.<\/li>\n<\/ul>\n\n\n\n

    Ultimately, Onsite Survey insight strengthens Conversion & Measurement<\/strong> maturity: it ties outcomes (conversion, revenue) to human reasons, making CRO<\/strong> more predictable and less opinion-driven.<\/p>\n\n\n\n

    How Onsite Survey Works<\/h2>\n\n\n\n

    In practice, an Onsite Survey<\/strong> works through a repeatable loop that fits naturally into Conversion & Measurement<\/strong> and CRO<\/strong> workflows:<\/p>\n\n\n\n

      \n
    1. \n

      Trigger (when and to whom it appears)<\/strong>\n The survey is shown based on rules such as time on page, scroll depth, exit intent, returning visitor status, device type, traffic source, or funnel step (e.g., cart, checkout, pricing page).<\/p>\n<\/li>\n

    2. \n

      Collection (what is asked and how responses are captured)<\/strong>\n Visitors answer one or more questions. Responses can be multiple-choice (easy to quantify) plus an optional free-text field (rich insight). Surveys may also store contextual metadata like page URL, device, and referrer.<\/p>\n<\/li>\n

    3. \n

      Analysis (how insights are organized and validated)<\/strong>\n Responses are coded into themes (e.g., \u201cshipping cost,\u201d \u201ctrust,\u201d \u201cfeature missing,\u201d \u201cconfusing pricing\u201d). Then you compare themes against funnel metrics, segments, and cohorts in your Conversion & Measurement<\/strong> stack.<\/p>\n<\/li>\n

    4. \n

      Application (how feedback becomes action)<\/strong>\n Insights are used to:\n – prioritize UX fixes and content improvements,\n – define A\/B test hypotheses for CRO<\/strong>,\n – refine targeting and messaging across campaigns,\n – improve support documentation and onboarding.<\/p>\n<\/li>\n

    5. \n

      Outcome (how impact is measured)<\/strong>\n You measure changes in conversion rate, step completion, reduced abandonment, improved lead quality, and fewer support tickets\u2014closing the loop between survey feedback and measurable results.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

      Key Components of Onsite Survey<\/h2>\n\n\n\n

      A high-performing Onsite Survey<\/strong> program depends on a few essential elements:<\/p>\n\n\n\n

      Survey design (question strategy)<\/h3>\n\n\n\n
        \n
      • Goal alignment:<\/strong> Each survey should tie to a decision you can make (not just curiosity).<\/li>\n
      • Question types:<\/strong> Multiple-choice for quantification; free text for nuance.<\/li>\n
      • Neutral phrasing:<\/strong> Avoid leading questions that bias responses.<\/li>\n<\/ul>\n\n\n\n

        Targeting and triggers<\/h3>\n\n\n\n
          \n
        • Page-level rules (pricing, product, checkout)<\/li>\n
        • Funnel-step targeting (first-time vs returning, logged-in vs logged-out)<\/li>\n
        • Behavior-based triggers (exit intent, idle time, repeat visits)<\/li>\n<\/ul>\n\n\n\n

          Data handling and governance<\/h3>\n\n\n\n
            \n
          • Defined ownership (CRO, product, UX research, analytics)<\/li>\n
          • A cadence for review (weekly triage + monthly deep dive)<\/li>\n
          • A taxonomy for tagging themes so Conversion & Measurement<\/strong> reporting stays consistent<\/li>\n<\/ul>\n\n\n\n

            Integration with measurement<\/h3>\n\n\n\n
              \n
            • Linking themes to funnel steps and segments<\/li>\n
            • Using survey results to guide CRO<\/strong> backlogs and experimentation roadmaps<\/li>\n
            • Storing outputs in dashboards or reporting systems for visibility<\/li>\n<\/ul>\n\n\n\n

              Types of Onsite Survey<\/h2>\n\n\n\n

              While \u201cOnsite Survey\u201d is a single concept, it\u2019s commonly applied in a few distinct ways:<\/p>\n\n\n\n

              1) Intent surveys<\/h3>\n\n\n\n

              Used early in the journey to understand why visitors came and what they\u2019re trying to do.\nExample question: \u201cWhat brought you here today?\u201d<\/p>\n\n\n\n

              2) Objection and friction surveys<\/h3>\n\n\n\n

              Used on high-impact pages (pricing, cart, checkout) to identify what\u2019s preventing conversion.\nExample question: \u201cWhat\u2019s stopping you from completing your purchase?\u201d<\/p>\n\n\n\n

              3) Experience and usability surveys<\/h3>\n\n\n\n

              Used to diagnose confusion, missing information, or UX issues.\nExample question: \u201cDid you find what you were looking for?\u201d<\/p>\n\n\n\n

              4) Post-conversion surveys<\/h3>\n\n\n\n

              Triggered after a lead form submission or purchase to capture decision factors.\nExample question: \u201cWhat made you choose us today?\u201d<\/p>\n\n\n\n

              5) Customer effort \/ satisfaction surveys (onsite)<\/h3>\n\n\n\n

              Short measures of perceived effort or satisfaction, used carefully because they don\u2019t always explain why<\/em>.\nExample question: \u201cHow easy was it to complete your task?\u201d<\/p>\n\n\n\n

              These types map neatly into Conversion & Measurement<\/strong>: intent explains top-of-funnel traffic quality; friction reveals drop-off causes; post-conversion clarifies value drivers that can improve CRO<\/strong> messaging.<\/p>\n\n\n\n

              Real-World Examples of Onsite Survey<\/h2>\n\n\n\n

              Example 1: Ecommerce checkout abandonment<\/h3>\n\n\n\n

              A retailer sees a high cart-to-checkout drop-off in analytics. They deploy an Onsite Survey<\/strong> on the cart page triggered on exit intent: \u201cWhat stopped you from checking out?\u201d\nResults show two dominant themes: unexpected shipping cost and lack of delivery time estimates. In CRO<\/strong>, they test (a) showing shipping estimates earlier and (b) adding a delivery date range near the add-to-cart button. Conversion & Measurement<\/strong> validates impact through reduced abandonment and higher completed orders.<\/p>\n\n\n\n

              Example 2: B2B SaaS pricing page confusion<\/h3>\n\n\n\n

              A SaaS company notices high pricing page traffic but low demo requests. An Onsite Survey asks: \u201cWhat information is missing that would help you decide?\u201d\nVisitors repeatedly mention unclear user-based pricing and missing integration details. The team updates pricing explanations and adds an integrations section. In CRO<\/strong>, they test a revised pricing layout and measure demo conversion rate and lead quality in Conversion & Measurement<\/strong> dashboards.<\/p>\n\n\n\n

              Example 3: Content-to-lead funnel optimization<\/h3>\n\n\n\n

              A publisher uses an Onsite Survey on high-traffic guides: \u201cWhat best describes your role?\u201d and \u201cWhat are you trying to achieve?\u201d\nThey discover a large segment is small business owners seeking templates rather than strategy. They add a template CTA and adjust newsletter segmentation. Conversion & Measurement<\/strong> tracks improved email signups and downstream engagement, while CRO<\/strong> tests CTA placement and content upgrades.<\/p>\n\n\n\n

              Benefits of Using Onsite Survey<\/h2>\n\n\n\n

              An Onsite Survey<\/strong> delivers benefits that are hard to replicate with clickstream data alone:<\/p>\n\n\n\n

                \n
              • Better performance in CRO:<\/strong> More accurate hypotheses increase win rates and reduce \u201ctest and hope\u201d cycles.<\/li>\n
              • Lower research costs:<\/strong> You can gather directional insight without long research projects, especially for recurring questions.<\/li>\n
              • Improved efficiency:<\/strong> Teams waste less time debating causes when visitor feedback is visible and structured.<\/li>\n
              • Stronger customer experience:<\/strong> Fixing the exact issues visitors report reduces friction and builds trust.<\/li>\n
              • Clearer messaging:<\/strong> Free-text responses often provide the best copy cues for headings, FAQs, and ads\u2014supporting both acquisition and Conversion & Measurement<\/strong> outcomes.<\/li>\n<\/ul>\n\n\n\n

                Challenges of Onsite Survey<\/h2>\n\n\n\n

                An Onsite Survey is powerful, but it\u2019s not magic. Common pitfalls include:<\/p>\n\n\n\n

                  \n
                • Sampling bias:<\/strong> Not everyone responds; responders may skew toward extremes (very happy or very frustrated).<\/li>\n
                • Poor timing and targeting:<\/strong> Asking too early (no context) or too late (visitor already left) reduces usefulness.<\/li>\n
                • Low-quality questions:<\/strong> Leading, vague, or multi-part questions produce ambiguous data.<\/li>\n
                • Survey fatigue:<\/strong> Too many prompts can harm UX and even reduce conversions\u2014counterproductive for CRO<\/strong>.<\/li>\n
                • Weak linkage to measurement:<\/strong> If survey responses aren\u2019t tied back to segments and funnel steps, Conversion & Measurement<\/strong> teams can\u2019t quantify impact.<\/li>\n
                • Privacy and compliance constraints:<\/strong> Collecting personal data unnecessarily increases risk; anonymous feedback is often sufficient.<\/li>\n<\/ul>\n\n\n\n

                  Best Practices for Onsite Survey<\/h2>\n\n\n\n

                  To get reliable insight and support CRO<\/strong> outcomes, use these practices:<\/p>\n\n\n\n

                  Keep it short, specific, and decision-driven<\/h3>\n\n\n\n
                    \n
                  • Prefer 1\u20132 questions for high-traffic pages.<\/li>\n
                  • Ask what you can act on within weeks, not months.<\/li>\n<\/ul>\n\n\n\n

                    Use a balanced question format<\/h3>\n\n\n\n
                      \n
                    • Start with a multiple-choice question to categorize responses.<\/li>\n
                    • Add an optional \u201cOther (please specify)\u201d free-text field to capture nuance.<\/li>\n<\/ul>\n\n\n\n

                      Target high-leverage moments<\/h3>\n\n\n\n

                      Common high-value placements for an Onsite Survey<\/strong>:\n– Pricing page (objections, plan confusion)\n– Product detail pages (missing info, trust signals)\n– Cart\/checkout (abandonment reasons)\n– Lead forms (why they\u2019re in-market, urgency)<\/p>\n\n\n\n

                      Control frequency and avoid interrupting intent<\/h3>\n\n\n\n
                        \n
                      • Cap impressions per user\/session.<\/li>\n
                      • Avoid showing surveys during critical actions (payment entry, form completion).<\/li>\n<\/ul>\n\n\n\n

                        Build a tagging taxonomy and review cadence<\/h3>\n\n\n\n

                        For Conversion & Measurement<\/strong> discipline:\n– Define 8\u201315 theme tags (shipping, pricing, trust, UX, features, competitor, etc.).\n– Review weekly for quick wins; monthly for trend analysis.\n– Convert top themes into a CRO<\/strong> backlog with owners and due dates.<\/p>\n\n\n\n

                        Validate with behavioral data<\/h3>\n\n\n\n

                        Treat survey insights as hypotheses that should be cross-checked:\n– Compare responses by device, channel, and landing page.\n– Pair with funnel analysis, session replays, and error logs before making large changes.<\/p>\n\n\n\n

                        Tools Used for Onsite Survey<\/h2>\n\n\n\n

                        An Onsite Survey<\/strong> program typically uses tool categories rather than a single system. In mature Conversion & Measurement<\/strong> stacks, these categories work together:<\/p>\n\n\n\n

                          \n
                        • Onsite survey and feedback tools:<\/strong> Create surveys, define triggers, and export responses.<\/li>\n
                        • Web analytics tools:<\/strong> Segment by source\/medium, landing page, device, and funnel step; correlate responses with conversion performance.<\/li>\n
                        • Tag management systems:<\/strong> Deploy and control survey scripts and triggers consistently.<\/li>\n
                        • Product analytics (for SaaS):<\/strong> Tie feedback to in-app behaviors, activation milestones, and retention cohorts.<\/li>\n
                        • Experimentation platforms:<\/strong> Turn insights into A\/B tests as part of CRO<\/strong>.<\/li>\n
                        • CRM and marketing automation:<\/strong> For post-conversion surveys, connect responses to lead stages and pipeline (carefully, with consent and minimal personal data).<\/li>\n
                        • BI and reporting dashboards:<\/strong> Build trend reporting for themes, conversion impact, and qualitative highlights.<\/li>\n<\/ul>\n\n\n\n

                          The key is operational fit: Onsite Survey data should be easy to analyze and easy to bring into your Conversion & Measurement<\/strong> reporting rhythm.<\/p>\n\n\n\n

                          Metrics Related to Onsite Survey<\/h2>\n\n\n\n

                          Because an Onsite Survey is an insight tool, its success metrics should cover both data quality<\/strong> and business impact<\/strong>:<\/p>\n\n\n\n

                          Survey performance metrics<\/h3>\n\n\n\n
                            \n
                          • View rate (survey impressions vs eligible sessions)<\/li>\n
                          • Completion rate<\/li>\n
                          • Response rate<\/li>\n
                          • Drop-off per question (for multi-question surveys)<\/li>\n
                          • Time to complete (a proxy for friction)<\/li>\n<\/ul>\n\n\n\n

                            Insight quality metrics<\/h3>\n\n\n\n
                              \n
                            • Share of responses that fit a known theme (vs \u201cunclear\/other\u201d)<\/li>\n
                            • Theme concentration (are a few issues dominating?)<\/li>\n
                            • New theme discovery rate (are you learning something new over time?)<\/li>\n<\/ul>\n\n\n\n

                              CRO and Conversion & Measurement impact metrics<\/h3>\n\n\n\n
                                \n
                              • Conversion rate lift on targeted pages\/steps<\/li>\n
                              • Funnel step completion rate (e.g., cart \u2192 checkout \u2192 purchase)<\/li>\n
                              • Revenue per session \/ average order value (where relevant)<\/li>\n
                              • Lead quality indicators (sales acceptance, pipeline conversion)<\/li>\n
                              • Support\/contact rate reductions after fixes<\/li>\n<\/ul>\n\n\n\n

                                Future Trends of Onsite Survey<\/h2>\n\n\n\n

                                Onsite Survey practices are evolving alongside changes in Conversion & Measurement<\/strong>:<\/p>\n\n\n\n

                                  \n
                                • AI-assisted analysis:<\/strong> Automated clustering and summarization will speed up theme detection, especially for free-text responses, while teams still need human validation for nuance.<\/li>\n
                                • More personalization with guardrails:<\/strong> Surveys will increasingly adapt questions based on context (new vs returning, product category, journey stage) without becoming intrusive.<\/li>\n
                                • Privacy-first measurement:<\/strong> As regulations and browser changes reduce tracking options, first-party feedback like Onsite Survey responses becomes more valuable\u2014provided it avoids unnecessary personal data.<\/li>\n
                                • Tighter integration with experimentation:<\/strong> Expect faster loops where survey themes directly generate CRO<\/strong> test ideas, prioritized by estimated impact and frequency.<\/li>\n
                                • Better \u201cvoice of customer\u201d unification:<\/strong> Onsite Survey data will be combined with support tickets, chat logs, and reviews to create a single insight pipeline for Conversion & Measurement<\/strong> teams.<\/li>\n<\/ul>\n\n\n\n

                                  Onsite Survey vs Related Terms<\/h2>\n\n\n\n

                                  Onsite Survey vs Feedback Widget<\/h3>\n\n\n\n

                                  A feedback widget is usually an always-available button (\u201cGive feedback\u201d) and relies on self-motivated visitors. An Onsite Survey<\/strong> is proactively triggered and structured to answer specific CRO<\/strong> and Conversion & Measurement<\/strong> questions, often yielding more comparable data.<\/p>\n\n\n\n

                                  Onsite Survey vs User Testing<\/h3>\n\n\n\n

                                  User testing involves observing participants completing tasks (often moderated or recorded) and provides deep behavioral insight with small samples. An Onsite Survey provides broader, in-the-wild feedback at scale but with less observational depth. In CRO<\/strong>, they pair well: surveys identify issues; user tests explain behaviors behind them.<\/p>\n\n\n\n

                                  Onsite Survey vs NPS\/CSAT<\/h3>\n\n\n\n

                                  NPS and CSAT measure sentiment or loyalty, typically after an experience. An Onsite Survey<\/strong> is more flexible and can target specific pages, intents, or blockers. For Conversion & Measurement<\/strong>, NPS\/CSAT are outcome signals; Onsite Survey responses are diagnostic inputs.<\/p>\n\n\n\n

                                  Who Should Learn Onsite Survey<\/h2>\n\n\n\n
                                    \n
                                  • Marketers:<\/strong> Improve landing pages, align ad promises with onsite experience, and refine messaging using real visitor language.<\/li>\n
                                  • Analysts:<\/strong> Add qualitative context to funnels and segments, strengthening Conversion & Measurement<\/strong> narratives and recommendations.<\/li>\n
                                  • Agencies:<\/strong> Diagnose client performance faster and justify CRO<\/strong> roadmaps with direct customer evidence.<\/li>\n
                                  • Business owners and founders:<\/strong> Identify the few issues preventing growth without relying solely on internal assumptions.<\/li>\n
                                  • Developers and UX teams:<\/strong> Prioritize fixes based on observed friction and error patterns corroborated by visitor feedback.<\/li>\n<\/ul>\n\n\n\n

                                    Summary of Onsite Survey<\/h2>\n\n\n\n

                                    An Onsite Survey<\/strong> is a structured, targeted way to collect visitor feedback directly on a website. It matters because it explains the \u201cwhy\u201d behind conversion behavior, strengthening Conversion & Measurement<\/strong> decision-making and increasing the effectiveness of CRO<\/strong> efforts. When designed well\u2014short, timed correctly, and analyzed with a consistent taxonomy\u2014Onsite Survey insights lead to clearer hypotheses, better user experiences, and measurable improvements in conversion outcomes.<\/p>\n\n\n\n

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

                                    1) What is an Onsite Survey used for?<\/h3>\n\n\n\n

                                    An Onsite Survey<\/strong> is used to capture visitor intent, objections, and experience feedback at specific points on your website\u2014often to explain drop-offs, improve messaging, and generate CRO<\/strong> test ideas within your Conversion & Measurement<\/strong> program.<\/p>\n\n\n\n

                                    2) How many questions should an Onsite Survey have?<\/h3>\n\n\n\n

                                    For most pages, 1\u20132 questions works best. If you need more depth, use one multiple-choice question plus an optional free-text follow-up to preserve response quality and reduce friction.<\/p>\n\n\n\n

                                    3) Where should I place surveys to improve CRO?<\/h3>\n\n\n\n

                                    High-leverage placements include pricing pages, product pages, cart and checkout steps, and lead forms. These areas directly influence conversion outcomes, making them ideal for CRO<\/strong> and Conversion & Measurement<\/strong> learning loops.<\/p>\n\n\n\n

                                    4) Do onsite surveys hurt conversion rates?<\/h3>\n\n\n\n

                                    They can if they interrupt users, appear too often, or cover important UI elements. Use frequency caps, avoid showing during critical steps, and test different triggers to ensure the Onsite Survey<\/strong> supports rather than harms CRO<\/strong> performance.<\/p>\n\n\n\n

                                    5) How do I analyze free-text responses at scale?<\/h3>\n\n\n\n

                                    Start with a theme taxonomy (tags like pricing, shipping, trust, usability), then code responses weekly. Use automation to assist grouping, but validate themes manually so Conversion & Measurement<\/strong> decisions remain accurate.<\/p>\n\n\n\n

                                    6) What\u2019s the difference between survey feedback and analytics?<\/h3>\n\n\n\n

                                    Analytics tells you what users did (clicks, drop-offs, paths). An Onsite Survey<\/strong> tells you why they did it (confusion, missing info, concerns). Together they form a stronger Conversion & Measurement<\/strong> foundation for CRO<\/strong>.<\/p>\n\n\n\n

                                    7) What response rate is \u201cgood\u201d for an onsite survey?<\/h3>\n\n\n\n

                                    It varies by traffic volume, trigger, and audience, but \u201cgood\u201d is less important than consistency and actionable themes. Focus on whether the Onsite Survey<\/strong> reveals repeatable patterns that lead to measurable conversion improvements.<\/p>\n","protected":false},"excerpt":{"rendered":"

                                    An **Onsite Survey** is one of the most direct ways to understand *why* people behave the way they do on your website\u2014straight from the visitor, in the moment. In **Conversion & Measurement**, it fills a critical gap that analytics alone can\u2019t: quantitative tools show what happened, while an Onsite Survey helps explain the motivations, confusion, objections, and intent behind the clicks.<\/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-7171","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\/7171","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=7171"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/7171\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=7171"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=7171"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=7171"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}