{"id":6632,"date":"2026-03-23T06:18:54","date_gmt":"2026-03-23T06:18:54","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/reputation-testing-framework\/"},"modified":"2026-03-23T06:18:54","modified_gmt":"2026-03-23T06:18:54","slug":"reputation-testing-framework","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/reputation-testing-framework\/","title":{"rendered":"Reputation Testing Framework: What It Is, Key Features, Benefits, Use Cases, and How It Fits in Reputation Management"},"content":{"rendered":"\n

A Reputation Testing Framework<\/strong> is a structured way to measure, stress-test, and improve how your brand is perceived across channels\u2014before perception turns into revenue impact, churn, or a crisis. In Brand & Trust<\/strong>, it acts like quality assurance for credibility: you don\u2019t \u201chope\u201d customers trust you; you validate the signals that create trust.<\/p>\n\n\n\n

Modern Reputation Management<\/strong> is no longer limited to responding to bad reviews. It includes proactively testing messaging, monitoring narrative shifts, verifying search results, and ensuring customer experience matches promises. A Reputation Testing Framework<\/strong> matters because reputation is now shaped in public, at speed, and across many touchpoints\u2014search results, social platforms, marketplaces, media coverage, and even AI-generated summaries.<\/p>\n\n\n\n

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

A Reputation Testing Framework<\/strong> is a repeatable system for evaluating reputation risk and trust signals using defined inputs (data), methods (tests), owners (governance), and outcomes (actions). It helps you answer practical questions like:<\/p>\n\n\n\n

    \n
  • What are customers actually saying\u2014and is it trending up or down?<\/li>\n
  • Where is trust breaking in the journey (ads, onboarding, support, billing, product quality)?<\/li>\n
  • Are search results reinforcing confidence or amplifying complaints?<\/li>\n
  • Which issues are isolated incidents vs. systemic problems?<\/li>\n<\/ul>\n\n\n\n

    The core concept is simple: treat reputation as something you can test, measure, and improve<\/strong>, not just react to. The business meaning is even clearer\u2014reputation influences conversion rates, sales cycles, partnerships, hiring, pricing power, and crisis resilience.<\/p>\n\n\n\n

    Within Brand & Trust<\/strong>, a Reputation Testing Framework<\/strong> organizes how you validate credibility signals. Inside Reputation Management<\/strong>, it provides the operational backbone: what to monitor, what thresholds trigger action, and how to prove improvements over time.<\/p>\n\n\n\n

    Why Reputation Testing Framework Matters in Brand & Trust<\/h2>\n\n\n\n

    In Brand & Trust<\/strong>, reputation is a leading indicator. Waiting for a quarterly brand survey or a spike in negative reviews is usually too late. A Reputation Testing Framework<\/strong> creates early warning and continuous improvement.<\/p>\n\n\n\n

    Strategically, it helps you:<\/p>\n\n\n\n

      \n
    • Reduce risk<\/strong>: catch narrative shifts, product issues, or service failures early.<\/li>\n
    • Protect demand<\/strong>: prevent trust erosion that lowers conversion and increases price sensitivity.<\/li>\n
    • Improve marketing effectiveness<\/strong>: stronger trust signals lift performance across paid, organic, email, and partnerships.<\/li>\n
    • Build competitive advantage<\/strong>: when products look similar, reputation and credibility become differentiators.<\/li>\n<\/ul>\n\n\n\n

      For Reputation Management<\/strong>, the value is alignment. Teams stop arguing from anecdotes and start prioritizing issues with data, impact estimates, and clear ownership.<\/p>\n\n\n\n

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

      A Reputation Testing Framework<\/strong> can be run continuously (always-on monitoring) and periodically (structured audits). In practice, it often follows this workflow:<\/p>\n\n\n\n

        \n
      1. \n

        Input \/ trigger<\/strong>\n You collect signals from reviews, social mentions, support tickets, surveys, search results, media coverage, and campaign feedback. Triggers may include a product launch, pricing change, incident, influencer campaign, or unusual sentiment movement.<\/p>\n<\/li>\n

      2. \n

        Analysis \/ processing<\/strong>\n You classify signals by topic (shipping, reliability, ethics, privacy, customer service), severity, and reach. You validate whether the issue is real, localized, or systemic. You also segment by audience (new customers vs. power users, regions, plan types).<\/p>\n<\/li>\n

      3. \n

        Execution \/ application<\/strong>\n You run tests and interventions: update messaging, fix journey friction, improve response playbooks, adjust policy language, or change product experiences. You may also test content positioning, FAQ clarity, ad claims, or onboarding steps that commonly create misunderstandings.<\/p>\n<\/li>\n

      4. \n

        Output \/ outcome<\/strong>\n You produce prioritized actions, owners, timelines, and post-change measurement. The output should translate into Brand & Trust<\/strong> improvements (stronger credibility signals) and measurable Reputation Management<\/strong> outcomes (fewer escalations, better ratings, improved sentiment).<\/p>\n<\/li>\n<\/ol>\n\n\n\n

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

        A robust Reputation Testing Framework<\/strong> typically includes:<\/p>\n\n\n\n

        Data inputs (reputation signals)<\/h3>\n\n\n\n
          \n
        • Reviews and ratings (first-party and third-party platforms)<\/li>\n
        • Social mentions and comment threads<\/li>\n
        • Search results for brand terms (including \u201cbrand + reviews\u201d, \u201cbrand + scam\u201d, \u201cbrand + pricing\u201d)<\/li>\n
        • Customer support data (tickets, categories, resolution notes)<\/li>\n
        • Voice-of-customer surveys and feedback forms<\/li>\n
        • Media mentions and partner\/community posts<\/li>\n<\/ul>\n\n\n\n

          Processes (how testing happens)<\/h3>\n\n\n\n
            \n
          • Baseline reputation audit (what \u201cnormal\u201d looks like)<\/li>\n
          • Ongoing monitoring and alerting rules<\/li>\n
          • Issue classification and root-cause analysis<\/li>\n
          • Content and messaging validation (claims, disclaimers, clarity)<\/li>\n
          • Response and escalation playbooks<\/li>\n<\/ul>\n\n\n\n

            Metrics and thresholds<\/h3>\n\n\n\n
              \n
            • Sentiment and topic trends<\/li>\n
            • Review velocity and rating distribution shifts<\/li>\n
            • Response time and resolution quality measures<\/li>\n
            • Trust indicators across the funnel (CTR, conversion, churn)<\/li>\n<\/ul>\n\n\n\n

              Governance (who owns what)<\/h3>\n\n\n\n
                \n
              • Clear ownership across marketing, comms, support, product, legal, and HR<\/li>\n
              • Decision rights (who can publish statements, approve refunds, change policies)<\/li>\n
              • Cadence: weekly triage + monthly deep dives + quarterly audits<\/li>\n<\/ul>\n\n\n\n

                This governance layer is where Brand & Trust<\/strong> becomes operational, and where Reputation Management<\/strong> becomes scalable.<\/p>\n\n\n\n

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

                There isn\u2019t one universal standard, but most Reputation Testing Framework<\/strong> approaches fall into a few practical models:<\/p>\n\n\n\n

                Proactive vs. reactive frameworks<\/h3>\n\n\n\n
                  \n
                • Proactive<\/strong>: continuous monitoring, pre-launch message testing, trust-signal optimization.<\/li>\n
                • Reactive<\/strong>: incident response, crisis triage, rapid mitigation, post-mortems.<\/li>\n<\/ul>\n\n\n\n

                  Channel-based frameworks<\/h3>\n\n\n\n

                  Designed around where trust is built (or lost): search reputation, review ecosystems, social platforms, app stores, marketplaces, and community forums. This matters because Brand & Trust<\/strong> signals behave differently by channel.<\/p>\n\n\n\n

                  Risk-based frameworks<\/h3>\n\n\n\n

                  Prioritize scenarios with the highest downside: safety, privacy, billing integrity, refunds, compliance claims, and customer harm. In Reputation Management<\/strong>, risk-based approaches prevent small issues from turning into headline events.<\/p>\n\n\n\n

                  Experiment-driven frameworks<\/h3>\n\n\n\n

                  Use controlled tests to validate which changes improve trust: landing page language, onboarding steps, policy copy, review request timing, or support workflows.<\/p>\n\n\n\n

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

                  Example 1: SaaS launch messaging and trust validation<\/h3>\n\n\n\n

                  A SaaS company launches a new AI feature. Using a Reputation Testing Framework<\/strong>, they monitor \u201challucination,\u201d \u201cprivacy,\u201d and \u201cdata usage\u201d topics in support tickets and social mentions. They test revised product copy, clearer data-handling explanations, and an updated onboarding checklist.\nOutcome: fewer confused tickets, improved trial-to-paid conversion, and stronger Brand & Trust<\/strong> signals in reviews\u2014supporting long-term Reputation Management<\/strong>.<\/p>\n\n\n\n

                  Example 2: Retail brand shipping delays and review containment<\/h3>\n\n\n\n

                  A retail brand sees a spike in one-star reviews tied to late deliveries. The Reputation Testing Framework<\/strong> links reviews to a specific carrier and region, then updates delivery estimates, adds proactive shipping notifications, and adjusts review response templates to include practical resolution steps.\nOutcome: reduced negative review velocity and improved rating recovery\u2014measurable Reputation Management<\/strong> gains without excessive discounting.<\/p>\n\n\n\n

                  Example 3: Employer brand and leadership communication<\/h3>\n\n\n\n

                  A growing company experiences negative employee commentary after a policy change. A Reputation Testing Framework<\/strong> evaluates narrative spread across professional networks, compares sentiment to recruiting funnel drop-off, and tests a more transparent leadership Q&A format.\nOutcome: improved candidate acceptance rates and reduced rumor amplification, reinforcing Brand & Trust<\/strong> with both talent and customers.<\/p>\n\n\n\n

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

                  A well-run Reputation Testing Framework<\/strong> delivers benefits that go beyond \u201clooking good\u201d:<\/p>\n\n\n\n

                    \n
                  • Performance improvements<\/strong>: higher conversion rates, better paid media efficiency, stronger organic click-through when SERP reputation improves.<\/li>\n
                  • Cost savings<\/strong>: fewer escalations, reduced refund leakage, less crisis spend, and lower customer acquisition costs when trust increases.<\/li>\n
                  • Efficiency gains<\/strong>: faster triage, clearer ownership, and fewer internal debates based on anecdotes.<\/li>\n
                  • Better customer experience<\/strong>: fewer surprises, clearer expectations, and more consistent support\u2014key drivers of Brand & Trust<\/strong>.<\/li>\n<\/ul>\n\n\n\n

                    In mature Reputation Management<\/strong>, the biggest win is consistency: you\u2019re not improvising each time sentiment shifts.<\/p>\n\n\n\n

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

                    A Reputation Testing Framework<\/strong> can fail if teams underestimate real constraints:<\/p>\n\n\n\n

                      \n
                    • Data quality and bias<\/strong>: reviews and social chatter skew negative and may not represent the full customer base.<\/li>\n
                    • Attribution limits<\/strong>: it can be hard to prove which change caused a sentiment shift, especially alongside product updates or seasonality.<\/li>\n
                    • Siloed ownership<\/strong>: marketing sees messaging problems, support sees ticket volume, product sees bugs\u2014without shared prioritization.<\/li>\n
                    • Overreaction risk<\/strong>: chasing every mention can create inconsistent messaging and distract from high-impact fixes.<\/li>\n
                    • Measurement drift<\/strong>: changes in platform algorithms or moderation policies can alter visibility, affecting Brand & Trust<\/strong> signals without any brand-side change.<\/li>\n<\/ul>\n\n\n\n

                      Recognizing these limits is part of responsible Reputation Management<\/strong>.<\/p>\n\n\n\n

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

                      Use these practices to make a Reputation Testing Framework<\/strong> reliable and scalable:<\/p>\n\n\n\n

                        \n
                      1. \n

                        Define what \u201ctrust\u201d means for your category<\/strong>\n Trust signals differ by industry: reliability and support in SaaS, authenticity in consumer goods, safety and privacy in fintech\/health.<\/p>\n<\/li>\n

                      2. \n

                        Create a reputation baseline before you optimize<\/strong>\n Document current sentiment, review distributions, top complaint themes, and branded search results. Without a baseline, Brand & Trust<\/strong> improvements are hard to prove.<\/p>\n<\/li>\n

                      3. \n

                        Use clear triage rules<\/strong>\n Classify issues by severity (harm, legal risk, revenue impact), reach (how many people see it), and recurrence (one-off vs. pattern).<\/p>\n<\/li>\n

                      4. \n

                        Tie tests to root causes, not symptoms<\/strong>\n If reviews complain about \u201cmisleading pricing,\u201d don\u2019t just respond faster\u2014fix pricing pages, checkout clarity, and expectation-setting.<\/p>\n<\/li>\n

                      5. \n

                        Close the loop with stakeholders<\/strong>\n Feed insights into product roadmaps, support training, and campaign QA. This is where Reputation Management<\/strong> becomes cross-functional.<\/p>\n<\/li>\n

                      6. \n

                        Measure before\/after with time windows<\/strong>\n Compare trends across consistent periods (e.g., 4 weeks pre-change vs. 4 weeks post-change) and segment by channel.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

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

                        A Reputation Testing Framework<\/strong> is enabled by tool categories rather than a single platform. Common groups include:<\/p>\n\n\n\n

                          \n
                        • Social listening and monitoring tools<\/strong>: track mentions, topics, and share-of-voice; detect spikes that threaten Brand & Trust<\/strong>.<\/li>\n
                        • Review management and feedback tools<\/strong>: monitor rating trends, response workflows, and location\/store-level performance.<\/li>\n
                        • SEO tools and search monitoring<\/strong>: evaluate branded queries, SERP composition, and reputation-related keywords that affect click behavior.<\/li>\n
                        • Analytics platforms<\/strong>: connect trust signals to funnel outcomes (bounce rate, conversion, retention).<\/li>\n
                        • CRM and support systems<\/strong>: analyze ticket categories, resolution times, escalation reasons, and customer sentiment notes.<\/li>\n
                        • Survey and voice-of-customer systems<\/strong>: collect structured feedback to balance the bias of public channels.<\/li>\n
                        • Reporting dashboards<\/strong>: unify Reputation Management<\/strong> metrics with marketing and product KPIs for shared decision-making.<\/li>\n<\/ul>\n\n\n\n

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

                          Choose metrics that connect perception to business outcomes. A practical Reputation Testing Framework<\/strong> often tracks:<\/p>\n\n\n\n

                          Brand & Trust metrics<\/h3>\n\n\n\n
                            \n
                          • Review rating average and distribution (not just the mean)<\/li>\n
                          • Review volume and velocity (rate of new reviews)<\/li>\n
                          • Topic frequency (top complaint drivers and emerging themes)<\/li>\n
                          • Sentiment trend over time (by channel and audience segment)<\/li>\n
                          • Branded search reputation indicators (presence of negative modifiers, SERP page composition)<\/li>\n<\/ul>\n\n\n\n

                            Reputation Management operations metrics<\/h3>\n\n\n\n
                              \n
                            • Response time to reviews and social inquiries<\/li>\n
                            • Resolution time for reputation-impacting issues<\/li>\n
                            • Escalation rate and repeat-contact rate<\/li>\n
                            • Ratio of resolved complaints to public complaints (containment effectiveness)<\/li>\n<\/ul>\n\n\n\n

                              Business impact metrics<\/h3>\n\n\n\n
                                \n
                              • Conversion rate changes on high-intent pages<\/li>\n
                              • Churn\/retention shifts after major fixes<\/li>\n
                              • Customer acquisition cost changes correlated with trust improvements<\/li>\n
                              • Sales cycle length and win rate (for B2B) as Brand & Trust<\/strong> strengthens<\/li>\n<\/ul>\n\n\n\n

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

                                A Reputation Testing Framework<\/strong> is evolving as reputation formation changes:<\/p>\n\n\n\n

                                  \n
                                • AI-driven summarization<\/strong>: audiences increasingly consume \u201csnapshots\u201d of brand sentiment. Testing how your brand is summarized across channels will become part of Brand & Trust<\/strong> work.<\/li>\n
                                • Automation for triage<\/strong>: faster detection of anomalies, smarter routing to owners, and standardized first responses\u2014while keeping humans responsible for judgment.<\/li>\n
                                • Personalization and segmentation<\/strong>: reputation won\u2019t be one score; it will vary by persona, region, and product line, pushing Reputation Management<\/strong> toward more granular reporting.<\/li>\n
                                • Privacy and measurement constraints<\/strong>: less third-party data means heavier reliance on first-party feedback, support insights, and controlled surveys.<\/li>\n
                                • Proof and transparency<\/strong>: expect greater demand for verifiable claims (policies, sourcing, security posture). A Reputation Testing Framework<\/strong> will increasingly include \u201cclaim validation\u201d audits for marketing and product statements.<\/li>\n<\/ul>\n\n\n\n

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

                                  Reputation Testing Framework vs social listening<\/h3>\n\n\n\n

                                  Social listening is a data collection and monitoring practice<\/strong>. A Reputation Testing Framework<\/strong> includes social listening but adds governance, thresholds, experiments, and business impact measurement for Reputation Management<\/strong>.<\/p>\n\n\n\n

                                  Reputation Testing Framework vs brand audit<\/h3>\n\n\n\n

                                  A brand audit is often periodic and broader (identity, messaging, positioning). A Reputation Testing Framework<\/strong> is more continuous and operational\u2014focused on trust signals, risk, and rapid improvement within Brand & Trust<\/strong>.<\/p>\n\n\n\n

                                  Reputation Testing Framework vs crisis communication plan<\/h3>\n\n\n\n

                                  A crisis plan defines how you respond during an incident. A Reputation Testing Framework<\/strong> covers crisis readiness but also proactive testing to reduce the likelihood and severity of crises\u2014making it a broader Reputation Management<\/strong> system.<\/p>\n\n\n\n

                                  Who Should Learn Reputation Testing Framework<\/h2>\n\n\n\n
                                    \n
                                  • Marketers<\/strong>: to prevent campaigns from creating credibility gaps and to improve performance by strengthening Brand & Trust<\/strong> signals.<\/li>\n
                                  • Analysts<\/strong>: to turn messy reputation data into decision-ready insights and measurable outcomes.<\/li>\n
                                  • Agencies<\/strong>: to operationalize ongoing Reputation Management<\/strong> for clients with clear reporting and defensible prioritization.<\/li>\n
                                  • Business owners and founders<\/strong>: to protect growth, reduce downside risk, and build trust that compounds over time.<\/li>\n
                                  • Developers and product teams<\/strong>: because reliability, UX clarity, security, and incident handling are reputation drivers that a Reputation Testing Framework<\/strong> can surface and quantify.<\/li>\n<\/ul>\n\n\n\n

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

                                    A Reputation Testing Framework<\/strong> is a structured, repeatable approach to measuring and improving reputation through defined data inputs, analysis methods, interventions, and outcomes. It matters because Brand & Trust<\/strong> directly influences conversion, retention, and resilience. As a core practice within Reputation Management<\/strong>, it replaces reactive guesswork with governance, prioritization, and measurable improvements across channels.<\/p>\n\n\n\n

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

                                    1) What is a Reputation Testing Framework in simple terms?<\/h3>\n\n\n\n

                                    A Reputation Testing Framework<\/strong> is a system for collecting reputation signals (reviews, mentions, search results, support issues), analyzing them consistently, and taking actions that improve trust and reduce risk.<\/p>\n\n\n\n

                                    2) How is Reputation Testing Framework different from just monitoring reviews?<\/h3>\n\n\n\n

                                    Review monitoring is one input. A Reputation Testing Framework<\/strong> adds root-cause analysis, testing (message and experience changes), ownership, thresholds, and measurement tied to Brand & Trust<\/strong> outcomes.<\/p>\n\n\n\n

                                    3) Which teams should own Reputation Management with a testing framework?<\/h3>\n\n\n\n

                                    Reputation Management<\/strong> should be cross-functional. Marketing or comms often coordinates, but support, product, legal\/compliance, and leadership need defined roles and escalation paths inside the Reputation Testing Framework<\/strong>.<\/p>\n\n\n\n

                                    4) How often should you run a Reputation Testing Framework?<\/h3>\n\n\n\n

                                    Most organizations use always-on monitoring plus a weekly triage rhythm and a monthly or quarterly deep-dive. The right cadence depends on volume of mentions, customer base size, and risk exposure in Brand & Trust<\/strong>.<\/p>\n\n\n\n

                                    5) What are the best metrics to start with?<\/h3>\n\n\n\n

                                    Start with review rating distribution, review velocity, top complaint themes, response time, and branded search reputation indicators. Then connect these to conversion, churn, or win rate to prove Reputation Management<\/strong> impact.<\/p>\n\n\n\n

                                    6) Can small businesses use a Reputation Testing Framework without big budgets?<\/h3>\n\n\n\n

                                    Yes. A lightweight Reputation Testing Framework<\/strong> can rely on consistent manual checks, simple dashboards, structured tagging of feedback, and a clear response playbook\u2014then expand tooling as volume grows.<\/p>\n\n\n\n

                                    7) What\u2019s the biggest mistake companies make in Brand & Trust testing?<\/h3>\n\n\n\n

                                    Over-focusing on surface sentiment while ignoring root causes. Sustainable Brand & Trust<\/strong> improvements come from fixing the underlying experience\u2014product reliability, clarity, and support\u2014not just better replies.<\/p>\n","protected":false},"excerpt":{"rendered":"

                                    A **Reputation Testing Framework** is a structured way to measure, stress-test, and improve how your brand is perceived across channels\u2014before perception turns into revenue impact, churn, or a crisis. In **Brand & Trust**, it acts like quality assurance for credibility: you don\u2019t \u201chope\u201d customers trust you; you validate the signals that create trust.<\/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":[1885],"tags":[],"class_list":["post-6632","post","type-post","status-publish","format-standard","hentry","category-reputation-management"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/6632","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=6632"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/6632\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=6632"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=6632"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=6632"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}