{"id":6588,"date":"2026-03-23T04:42:51","date_gmt":"2026-03-23T04:42:51","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/review-gating-policy\/"},"modified":"2026-03-23T04:42:51","modified_gmt":"2026-03-23T04:42:51","slug":"review-gating-policy","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/review-gating-policy\/","title":{"rendered":"Review Gating Policy: What It Is, Key Features, Benefits, Use Cases, and How It Fits in Reputation Management"},"content":{"rendered":"\n

A Review Gating Policy<\/strong> is the set of rules\u2014usually defined by review platforms and reinforced by internal company governance\u2014that determines what is and isn\u2019t allowed when asking customers for public reviews. In Brand & Trust<\/strong>, it\u2019s a big deal because reviews influence click-through rates, conversion, local visibility, and customer confidence. In Reputation Management<\/strong>, it\u2019s even more critical: the way you collect reviews can be just as important as the reviews themselves.<\/p>\n\n\n\n

Modern buyers are highly sensitive to manipulation. A strong Review Gating Policy<\/strong> helps ensure your review acquisition methods are fair, transparent, and compliant\u2014reducing the risk of review removal, listing suspensions, and long-term damage to Brand & Trust<\/strong>.<\/p>\n\n\n\n

\n\n\n\n

What Is Review Gating Policy?<\/h2>\n\n\n\n

A Review Gating Policy<\/strong> is a guideline that prohibits or restricts \u201cgating\u201d behaviors\u2014most commonly, filtering who gets asked to leave a public review based on whether you expect positive feedback<\/strong>. In practice, review gating often looks like routing happy customers to Google, industry directories, or app stores, while directing unhappy customers to private support channels so they don\u2019t post publicly.<\/p>\n\n\n\n

The core concept is simple: public review requests should not be selectively targeted to create a biased rating outcome<\/strong>. Many major platforms consider review gating deceptive because it distorts the authenticity of marketplace signals.<\/p>\n\n\n\n

From a business perspective, Review Gating Policy<\/strong> sits at the intersection of growth and ethics. It affects how marketing teams run lifecycle campaigns, how customer success teams close the loop on issues, and how leadership protects Brand & Trust<\/strong>. Within Reputation Management<\/strong>, it becomes a compliance and operational discipline: collecting reviews in a way that is representative, defensible, and sustainable.<\/p>\n\n\n\n

\n\n\n\n

Why Review Gating Policy Matters in Brand & Trust<\/h2>\n\n\n\n

A clear Review Gating Policy<\/strong> protects the credibility of your brand\u2019s \u201csocial proof.\u201d When customers see a review profile that feels too perfect\u2014or discover manipulative tactics\u2014Brand & Trust<\/strong> can erode quickly.<\/p>\n\n\n\n

It also creates measurable business value:<\/p>\n\n\n\n

    \n
  • Stronger long-term conversion performance:<\/strong> Authentic review patterns build confidence more effectively than artificially inflated ratings.<\/li>\n
  • Lower platform risk:<\/strong> Avoiding prohibited gating reduces review takedowns and account penalties that can disrupt acquisition.<\/li>\n
  • Better customer intelligence:<\/strong> If you only solicit reviews from promoters, you lose public and private signals that can improve product, service, and support.<\/li>\n
  • Competitive advantage:<\/strong> Many competitors still rely on borderline tactics. A compliant approach becomes a durable Reputation Management<\/strong> advantage because it scales without penalties.<\/li>\n<\/ul>\n\n\n\n

    In short, Review Gating Policy<\/strong> is not \u201cred tape.\u201d It is a strategic foundation for consistent Brand & Trust<\/strong> and credible Reputation Management<\/strong> outcomes.<\/p>\n\n\n\n

    \n\n\n\n

    How Review Gating Policy Works<\/h2>\n\n\n\n

    A Review Gating Policy<\/strong> is more of a real-world operating standard than a single tool. Here\u2019s how it typically works in practice:<\/p>\n\n\n\n

      \n
    1. \n

      Input \/ Trigger<\/strong>\n A customer milestone occurs: purchase completion, onboarding completion, renewal, closed support ticket, delivery confirmation, or in-app engagement threshold.<\/p>\n<\/li>\n

    2. \n

      Analysis \/ Decision Rules<\/strong>\n Teams decide how<\/em> to ask for feedback. A compliant Review Gating Policy<\/strong> avoids rules like \u201conly send review links to 9\u201310 NPS scorers.\u201d Instead, it sets guardrails that keep review requests fair and representative.<\/p>\n<\/li>\n

    3. \n

      Execution \/ Application<\/strong>\n Requests go out via email, SMS, in-app prompts, or post-service kiosks. The policy governs wording, timing, eligible segments, and whether the process includes incentives (often prohibited by platforms).<\/p>\n<\/li>\n

    4. \n

      Output \/ Outcome<\/strong>\n You receive public reviews across platforms and private feedback through support channels. In Reputation Management<\/strong>, you also track compliance: removals, disputes, and response workflows that protect Brand & Trust<\/strong>.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

      \n\n\n\n

      Key Components of Review Gating Policy<\/h2>\n\n\n\n

      A robust Review Gating Policy<\/strong> is built from governance plus execution details. Key components often include:<\/p>\n\n\n\n

        \n
      • Platform compliance rules:<\/strong> Internal documentation summarizing major review platform expectations (e.g., no selective solicitation, no coercion, no undisclosed incentives).<\/li>\n
      • Audience eligibility criteria (non-discriminatory):<\/strong> Clear guidance on when<\/em> a customer can be asked (after service completion, after issue resolution), not whether they\u2019re likely to be positive<\/em>.<\/li>\n
      • Approved templates and language:<\/strong> Copy that avoids pressure (\u201cLeave us 5 stars\u201d), avoids conditional phrasing (\u201cIf you loved us\u2026\u201d), and stays respectful.<\/li>\n
      • Channel and timing standards:<\/strong> When to ask, how often, and how to prevent over-solicitation fatigue.<\/li>\n
      • Routing rules for support vs reviews:<\/strong> You can invite all customers to share feedback privately, but the Review Gating Policy<\/strong> must avoid using private feedback as a \u201cfilter\u201d that blocks public review opportunities.<\/li>\n
      • Ownership and governance:<\/strong> Roles across marketing, CX\/support, legal\/compliance, and location managers (for multi-location brands).<\/li>\n
      • Auditability:<\/strong> Logging of sends, segments, templates, and changes\u2014important for Reputation Management<\/strong> troubleshooting.<\/li>\n
      • Training and enforcement:<\/strong> Onboarding for frontline teams to prevent well-meaning but risky behavior.<\/li>\n<\/ul>\n\n\n\n

        These components help Brand & Trust<\/strong> by making review collection predictable, fair, and consistent.<\/p>\n\n\n\n

        \n\n\n\n

        Types of Review Gating Policy<\/h2>\n\n\n\n

        \u201cTypes\u201d usually refer to how the policy is applied<\/strong>, not a formal industry taxonomy. Common distinctions include:<\/p>\n\n\n\n

        Platform-enforced vs internal governance<\/h3>\n\n\n\n
          \n
        • Platform-enforced policy:<\/strong> Rules set by review sites and app stores; violations can lead to removal of reviews or account actions. <\/li>\n
        • Internal Review Gating Policy:<\/strong> Your company\u2019s playbook that interprets platform rules and sets operational standards for Reputation Management<\/strong>.<\/li>\n<\/ul>\n\n\n\n

          Preventive vs corrective approaches<\/h3>\n\n\n\n
            \n
          • Preventive:<\/strong> Design campaigns and flows so gating can\u2019t happen (approved templates, locked automation, audits). <\/li>\n
          • Corrective:<\/strong> Remediate after the fact (stop risky campaigns, retrain teams, document changes, request reinstatements where appropriate).<\/li>\n<\/ul>\n\n\n\n

            Centralized vs decentralized execution<\/h3>\n\n\n\n
              \n
            • Centralized:<\/strong> Corporate controls tools and templates, reducing risk and improving consistency in Brand & Trust<\/strong>. <\/li>\n
            • Decentralized:<\/strong> Locations\/teams run their own requests; faster but riskier without strong controls.<\/li>\n<\/ul>\n\n\n\n
              \n\n\n\n

              Real-World Examples of Review Gating Policy<\/h2>\n\n\n\n

              Example 1: SaaS NPS flow that crosses the line\u2014and how to fix it<\/h3>\n\n\n\n

              A SaaS company sends an NPS survey after onboarding. Promoters automatically get a prompt to review on a public software directory, while detractors get routed to support with no public option. That\u2019s a classic violation pattern addressed by many Review Gating Policy<\/strong> standards.<\/p>\n\n\n\n

              Compliant alternative:<\/strong> send the NPS survey to all customers, use it to prioritize outreach, and separately invite all eligible customers<\/em> to leave a public review at an appropriate time (for example, after onboarding completion or after a support resolution). This strengthens Brand & Trust<\/strong> without distorting review outcomes\u2014good Reputation Management<\/strong> hygiene.<\/p>\n\n\n\n

              Example 2: Local services business using SMS requests<\/h3>\n\n\n\n

              A home services company texts only customers who verbally praised the technician, asking them to review on Google, while unhappy customers receive no request. This selective solicitation is risky under a strict Review Gating Policy<\/strong> approach.<\/p>\n\n\n\n

              Compliant alternative:<\/strong> text every completed-job customer with a neutral request, plus an option to contact support. You\u2019re allowed to improve service recovery; you\u2019re not allowed to make public review access conditional.<\/p>\n\n\n\n

              Example 3: Ecommerce post-purchase email sequencing<\/h3>\n\n\n\n

              An ecommerce brand triggers review requests only when delivery feedback is positive. That can function as gating if negative respondents are excluded from the public review ask.<\/p>\n\n\n\n

              Compliant alternative:<\/strong> ask all customers to review the product after a consistent time window. Use customer service workflows to address issues, but keep the public review invitation consistent. This improves Brand & Trust<\/strong> signals and keeps Reputation Management<\/strong> scalable.<\/p>\n\n\n\n

              \n\n\n\n

              Benefits of Using Review Gating Policy<\/h2>\n\n\n\n

              A well-implemented Review Gating Policy<\/strong> delivers benefits beyond \u201cstaying out of trouble\u201d:<\/p>\n\n\n\n

                \n
              • More credible social proof:<\/strong> Authentic distribution of feedback builds durable Brand & Trust<\/strong>.<\/li>\n
              • Reduced removal and penalty risk:<\/strong> Lower chance of lost reviews, suppressed listings, or reduced visibility caused by non-compliance.<\/li>\n
              • Operational efficiency:<\/strong> Standard templates and automation reduce ad hoc decision-making and frontline inconsistency.<\/li>\n
              • Improved customer experience:<\/strong> Neutral, respectful review requests feel less manipulative and can reduce complaint volume.<\/li>\n
              • Better insight loops:<\/strong> Representative reviews plus private feedback support product improvement and smarter Reputation Management<\/strong> prioritization.<\/li>\n<\/ul>\n\n\n\n
                \n\n\n\n

                Challenges of Review Gating Policy<\/h2>\n\n\n\n

                Even when the intent is good, implementing Review Gating Policy<\/strong> can be difficult:<\/p>\n\n\n\n

                  \n
                • Legacy processes that \u201cworked\u201d:<\/strong> Teams may resist changing promoter-only flows that inflated ratings in the past.<\/li>\n
                • Tooling limitations:<\/strong> Some systems make it easy to segment by satisfaction score; enforcing non-gating rules may require workflow redesign.<\/li>\n
                • Franchise or multi-location complexity:<\/strong> Decentralized teams can introduce inconsistent practices that undermine Brand & Trust<\/strong>.<\/li>\n
                • Attribution and timing:<\/strong> Finding the right moment to ask without bias (and without spamming) requires testing and coordination.<\/li>\n
                • Measurement ambiguity:<\/strong> It can be hard to prove a campaign is \u201crepresentative,\u201d so Reputation Management<\/strong> needs clear internal definitions and audit trails.<\/li>\n<\/ul>\n\n\n\n
                  \n\n\n\n

                  Best Practices for Review Gating Policy<\/h2>\n\n\n\n

                  To make Review Gating Policy<\/strong> effective and practical, focus on execution details:<\/p>\n\n\n\n

                    \n
                  • Ask broadly and consistently:<\/strong> Use non-discriminatory eligibility (e.g., completed transaction) rather than satisfaction-based routing.<\/li>\n
                  • Separate feedback from public reviews:<\/strong> Collect private feedback to improve service, but don\u2019t use it to decide who gets a public review link.<\/li>\n
                  • Use neutral language:<\/strong> Avoid \u201c5-star\u201d prompts, guilt framing, or pressure. Keep it short and optional.<\/li>\n
                  • Control frequency:<\/strong> Set caps (per customer and per timeframe) to protect experience and Brand & Trust<\/strong>.<\/li>\n
                  • Document approvals:<\/strong> Maintain an internal policy doc and approved templates; update it when platforms change expectations.<\/li>\n
                  • Train frontline teams:<\/strong> Especially in retail, hospitality, healthcare, and services where casual verbal requests can become non-compliant.<\/li>\n
                  • Monitor for drift:<\/strong> Audit automation rules, segmentation, and template edits. This is ongoing Reputation Management<\/strong>, not a one-time setup.<\/li>\n
                  • Plan service recovery ethically:<\/strong> You can fix problems quickly and invite updated feedback later, but avoid \u201creview suppression\u201d tactics.<\/li>\n<\/ul>\n\n\n\n
                    \n\n\n\n

                    Tools Used for Review Gating Policy<\/h2>\n\n\n\n

                    A Review Gating Policy<\/strong> is operationalized through systems that control who gets asked, what they see, and what gets logged. Common tool categories include:<\/p>\n\n\n\n

                      \n
                    • CRM systems:<\/strong> Track customer status, lifecycle milestones, and consent\u2014key inputs for compliant review requests.<\/li>\n
                    • Marketing automation:<\/strong> Email\/SMS workflows, suppression lists, frequency caps, and template governance.<\/li>\n
                    • Customer support\/ticketing platforms:<\/strong> Ensure review asks aren\u2019t sent during unresolved issues; tie requests to resolution events (without filtering by sentiment).<\/li>\n
                    • Customer feedback tools:<\/strong> NPS\/CSAT collection for internal improvement\u2014useful for Reputation Management<\/strong> as long as it isn\u2019t used as a public review gate.<\/li>\n
                    • Review monitoring and response platforms:<\/strong> Centralize review intake, response SLAs, escalation, and reporting that supports Brand & Trust<\/strong>.<\/li>\n
                    • Analytics and reporting dashboards:<\/strong> Track review velocity, channel performance, and compliance indicators across brands or locations.<\/li>\n<\/ul>\n\n\n\n

                      The goal is controlled consistency: tools should enforce your Review Gating Policy<\/strong>, not make it easy to bypass.<\/p>\n\n\n\n

                      \n\n\n\n

                      Metrics Related to Review Gating Policy<\/h2>\n\n\n\n

                      To manage Review Gating Policy<\/strong> in a measurable way, track both performance and compliance:<\/p>\n\n\n\n

                        \n
                      • Review volume and velocity:<\/strong> Reviews per week\/month and changes after campaign updates.<\/li>\n
                      • Rating distribution:<\/strong> Not just the average\u2014look for unnatural skews that can raise internal red flags for Reputation Management<\/strong>.<\/li>\n
                      • Request-to-review conversion rate:<\/strong> How many review requests yield published reviews, by channel (email, SMS, in-app).<\/li>\n
                      • Platform mix:<\/strong> Diversity of review sources (maps, directories, app stores). Overdependence can be risky.<\/li>\n
                      • Response rate and response time:<\/strong> Speed and consistency of replies, which directly affects Brand & Trust<\/strong>.<\/li>\n
                      • Removal\/flag rate:<\/strong> Percentage of reviews removed or filtered; spikes can indicate policy violations or low-quality acquisition.<\/li>\n
                      • Customer sentiment trends:<\/strong> Themes in negative reviews that inform operational fixes.<\/li>\n
                      • Compliance audit metrics:<\/strong> Percentage of campaigns using approved templates, frequency cap adherence, and segmentation rule checks.<\/li>\n<\/ul>\n\n\n\n
                        \n\n\n\n

                        Future Trends of Review Gating Policy<\/h2>\n\n\n\n

                        Several shifts are shaping how Review Gating Policy<\/strong> evolves within Brand & Trust<\/strong>:<\/p>\n\n\n\n

                          \n
                        • AI-driven detection and moderation:<\/strong> Platforms increasingly use machine learning to detect suspicious patterns, selective solicitation, and coordinated campaigns.<\/li>\n
                        • Automation with stronger governance:<\/strong> Teams will rely more on locked templates, approval workflows, and audit logs to ensure compliant Reputation Management<\/strong> at scale.<\/li>\n
                        • Personalization (with constraints):<\/strong> Messaging will be more personalized, but policies will need to ensure personalization doesn\u2019t become selective solicitation in disguise.<\/li>\n
                        • Identity, fraud, and authenticity pressure:<\/strong> Expect stricter standards around fake reviews, employee reviews, and incentivized reviews\u2014raising the importance of a clear Review Gating Policy<\/strong>.<\/li>\n
                        • Privacy and consent expectations:<\/strong> Review requests must respect consent, communication preferences, and regional regulations, reinforcing Brand & Trust<\/strong> through respectful outreach.<\/li>\n<\/ul>\n\n\n\n
                          \n\n\n\n

                          Review Gating Policy vs Related Terms<\/h2>\n\n\n\n

                          Understanding adjacent concepts helps teams communicate clearly:<\/p>\n\n\n\n

                          Review Gating Policy vs review generation<\/h3>\n\n\n\n
                            \n
                          • Review generation<\/strong> is the broader practice of encouraging customers to leave reviews. <\/li>\n
                          • Review Gating Policy<\/strong> defines what review generation tactics are acceptable and compliant.<\/li>\n<\/ul>\n\n\n\n

                            Review Gating Policy vs NPS\/CSAT programs<\/h3>\n\n\n\n
                              \n
                            • NPS\/CSAT<\/strong> are feedback measurement systems designed for internal improvement. <\/li>\n
                            • A Review Gating Policy<\/strong> becomes relevant when teams use NPS\/CSAT scores to decide who gets a public review request\u2014often a risky move for Reputation Management<\/strong>.<\/li>\n<\/ul>\n\n\n\n

                              Review Gating Policy vs service recovery<\/h3>\n\n\n\n
                                \n
                              • Service recovery<\/strong> is fixing a bad experience. <\/li>\n
                              • Review Gating Policy<\/strong> clarifies that recovery is good, but using recovery as a mechanism to suppress public reviews is not.<\/li>\n<\/ul>\n\n\n\n
                                \n\n\n\n

                                Who Should Learn Review Gating Policy<\/h2>\n\n\n\n

                                Review Gating Policy<\/strong> knowledge is practical across roles:<\/p>\n\n\n\n

                                  \n
                                • Marketers:<\/strong> To design lifecycle and local campaigns that improve Brand & Trust<\/strong> without compliance risk.<\/li>\n
                                • Analysts:<\/strong> To interpret review data honestly, detect bias, and connect reviews to acquisition and retention.<\/li>\n
                                • Agencies:<\/strong> To protect clients from platform penalties and build scalable Reputation Management<\/strong> programs.<\/li>\n
                                • Business owners and founders:<\/strong> To avoid shortcuts that can backfire and to build credible social proof.<\/li>\n
                                • Developers:<\/strong> To implement review request flows, event triggers, and logging in a way that meets policy and governance requirements.<\/li>\n<\/ul>\n\n\n\n
                                  \n\n\n\n

                                  Summary of Review Gating Policy<\/h2>\n\n\n\n

                                  A Review Gating Policy<\/strong> is the practical set of rules that prevents selective review solicitation and other manipulative patterns. It matters because reviews are a core lever of Brand & Trust<\/strong>, and non-compliant tactics can lead to removals, penalties, and long-term credibility loss. In Reputation Management<\/strong>, it acts as a governance framework that standardizes how you request, collect, respond to, and learn from customer reviews\u2014at scale and with integrity.<\/p>\n\n\n\n

                                  \n\n\n\n

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

                                  1) What is a Review Gating Policy in simple terms?<\/h3>\n\n\n\n

                                  A Review Gating Policy<\/strong> is guidance that prevents asking only happy customers for public reviews (or steering unhappy customers away from public review sites). It aims to keep reviews fair, representative, and trustworthy.<\/p>\n\n\n\n

                                  2) Is review gating always prohibited?<\/h3>\n\n\n\n

                                  Many major platforms strongly discourage or prohibit selective solicitation patterns. Even when enforcement varies, gating is risky because it can lead to removals and undermine Brand & Trust<\/strong>.<\/p>\n\n\n\n

                                  3) Can we collect private feedback and still ask for public reviews?<\/h3>\n\n\n\n

                                  Yes. Private feedback is great for improvement. The key is that your Review Gating Policy<\/strong> should avoid using private feedback (or satisfaction scores) as a filter that determines who gets the public review invitation.<\/p>\n\n\n\n

                                  4) How does Review Gating Policy affect Reputation Management?<\/h3>\n\n\n\n

                                  In Reputation Management<\/strong>, the policy reduces compliance risk, improves the credibility of your review profile, and creates consistent operational rules for campaigns, locations, and customer-facing teams.<\/p>\n\n\n\n

                                  5) What wording should we avoid in review requests?<\/h3>\n\n\n\n

                                  Avoid pressuring language like \u201cLeave us a 5-star review,\u201d conditional prompts like \u201cIf you had a great experience\u2026,\u201d and any statement that implies reviews are required. Neutral, optional language supports Brand & Trust<\/strong>.<\/p>\n\n\n\n

                                  6) What\u2019s the best time to ask for a review without gating?<\/h3>\n\n\n\n

                                  Choose a consistent milestone (after delivery, after appointment completion, after onboarding, or after an issue is resolved) and apply it broadly. Consistency is a practical safeguard in any Review Gating Policy<\/strong>.<\/p>\n\n\n\n

                                  7) How do we audit whether our process is accidentally gating reviews?<\/h3>\n\n\n\n

                                  Review your automation rules and templates. If positive-score segments get public links while other segments do not, that\u2019s a gating pattern. Logging sends, segment criteria, and template versions makes Reputation Management<\/strong> audits much easier.<\/p>\n","protected":false},"excerpt":{"rendered":"

                                  A **Review Gating Policy** is the set of rules\u2014usually defined by review platforms and reinforced by internal company governance\u2014that determines what is and isn\u2019t allowed when asking customers for public reviews. In **Brand & Trust**, it\u2019s a big deal because reviews influence click-through rates, conversion, local visibility, and customer confidence. In **Reputation Management**, it\u2019s even more critical: the way you collect reviews can be just as important as the reviews themselves.<\/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-6588","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\/6588","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=6588"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/6588\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=6588"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=6588"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=6588"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}