{"id":11268,"date":"2026-04-01T15:55:40","date_gmt":"2026-04-01T15:55:40","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/shared-library\/"},"modified":"2026-04-01T15:55:40","modified_gmt":"2026-04-01T15:55:40","slug":"shared-library","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/shared-library\/","title":{"rendered":"Shared Library: What It Is, Key Features, Benefits, Use Cases, and How It Fits in SEM \/ Paid Search"},"content":{"rendered":"\n

A Shared Library<\/strong> is a centralized place inside an ad account (or across connected accounts, depending on the platform) where teams store reusable campaign resources\u2014then apply those resources consistently across multiple campaigns or ad groups. In Paid Marketing<\/strong>, it\u2019s one of the most practical ways to reduce repetitive work, prevent mistakes, and enforce standards at scale. In SEM \/ Paid Search<\/strong>, where dozens (or thousands) of keywords, audiences, exclusions, and settings can change weekly, a Shared Library helps teams stay aligned without slowing execution.<\/p>\n\n\n\n

Shared Library features matter because modern Paid Marketing<\/strong> is rarely \u201cone campaign at a time.\u201d It\u2019s ongoing iteration across brands, regions, channels, and product lines. A Shared Library supports that reality by making core building blocks reusable, governable, and easier to audit\u2014especially in high-spend SEM \/ Paid Search<\/strong> programs.<\/p>\n\n\n\n

What Is Shared Library?<\/h2>\n\n\n\n

In simple terms, a Shared Library<\/strong> is a platform area that holds shared assets (lists, sets, or configurations) that can be attached to multiple campaigns instead of being recreated repeatedly.<\/p>\n\n\n\n

The core concept is reuse with control<\/strong>:<\/p>\n\n\n\n

    \n
  • Reuse<\/strong>: Build a list (for example, exclusions) once and apply it many times.<\/li>\n
  • Control<\/strong>: Update it once and have the change propagate wherever it\u2019s used.<\/li>\n<\/ul>\n\n\n\n

    From a business perspective, a Shared Library is an operational scaling mechanism. It reduces the cost of managing complexity, improves consistency across campaigns, and makes performance more predictable. In Paid Marketing<\/strong>, this translates to fewer preventable spend leaks and faster deployment of best practices. In SEM \/ Paid Search<\/strong>, it often shows up in shared negative keyword lists, shared placement exclusions, shared budgets (in some platforms), and other shared resources that impact reach and efficiency.<\/p>\n\n\n\n

    Why Shared Library Matters in Paid Marketing<\/h2>\n\n\n\n

    A Shared Library is not just a convenience feature\u2014it\u2019s a strategic lever for teams that manage multiple campaigns, markets, or products.<\/p>\n\n\n\n

    Key reasons it matters in Paid Marketing<\/strong> include:<\/p>\n\n\n\n

      \n
    • Consistency across the account<\/strong>: Shared rules and lists reduce the \u201ccampaign-by-campaign drift\u201d that happens when different managers make different decisions.<\/li>\n
    • Speed with fewer errors<\/strong>: Duplicating lists manually invites version issues, typos, and missed updates.<\/li>\n
    • Stronger governance<\/strong>: You can define which resources are centrally managed and who can change them.<\/li>\n
    • Better learning transfer<\/strong>: When one team finds a high-value exclusion pattern, it can be rolled out broadly via the Shared Library.<\/li>\n<\/ul>\n\n\n\n

      In SEM \/ Paid Search<\/strong>, these advantages become a competitive edge because search landscapes change quickly. A team that can roll out new exclusions, brand protections, or targeting refinements across 50 campaigns in minutes will usually waste less spend and respond faster than a team doing the same work manually.<\/p>\n\n\n\n

      How Shared Library Works<\/h2>\n\n\n\n

      A Shared Library<\/strong> is most useful when you treat it as a \u201csystem of reusable decisions.\u201d While each platform differs, the practical workflow usually looks like this:<\/p>\n\n\n\n

        \n
      1. \n

        Input \/ trigger (why a shared asset is needed)<\/strong>\n A trigger might be a spike in irrelevant search terms, a new brand-safety policy, expansion into a new region, or a standardization initiative across Paid Marketing<\/strong>.<\/p>\n<\/li>\n

      2. \n

        Analysis \/ design (what belongs in the shared asset)<\/strong>\n Teams define rules and scope: What should be excluded? Which campaigns should inherit it? Are there exceptions? In SEM \/ Paid Search<\/strong>, this often includes separating \u201cglobal\u201d vs \u201ccampaign-specific\u201d exclusions.<\/p>\n<\/li>\n

      3. \n

        Execution \/ application (create once, apply many)<\/strong>\n The shared asset is created in the Shared Library and attached to the right campaigns\/ad groups. The goal is to minimize one-off copies that diverge over time.<\/p>\n<\/li>\n

      4. \n

        Output \/ outcome (measurable impact and ongoing updates)<\/strong>\n The best Shared Library assets are living artifacts. Teams review performance, add new items, remove overly restrictive entries, and document why changes were made\u2014supporting continuous improvement in Paid Marketing<\/strong>.<\/p>\n<\/li>\n<\/ol>\n\n\n\n

        Key Components of Shared Library<\/h2>\n\n\n\n

        A high-functioning Shared Library<\/strong> approach usually includes more than \u201ca place to store lists.\u201d The strongest programs pair platform features with process.<\/p>\n\n\n\n

        Common components include:<\/p>\n\n\n\n

          \n
        • \n

          Shared assets (the \u201cwhat\u201d)<\/strong>\n Examples include shared negative keyword lists, shared placement exclusion lists, shared audience sets, shared rules, or other reusable targeting\/exclusion objects supported by the platform.<\/p>\n<\/li>\n

        • \n

          Scope and hierarchy (the \u201cwhere\u201d)<\/strong>\n Clear decisions about what is global, what is brand-level, and what stays campaign-specific\u2014crucial for large SEM \/ Paid Search<\/strong> accounts.<\/p>\n<\/li>\n

        • \n

          Governance (the \u201cwho\u201d)<\/strong>\n Ownership, approvals, change logs, and permissions. In Paid Marketing<\/strong>, governance prevents accidental edits that can affect dozens of campaigns.<\/p>\n<\/li>\n

        • \n

          Documentation (the \u201cwhy\u201d)<\/strong>\n Naming conventions, list definitions, and rationale for inclusion. Documentation is what makes Shared Library assets teachable and auditable.<\/p>\n<\/li>\n

        • \n

          Measurement (the \u201cso what\u201d)<\/strong>\n A way to monitor impact: spend wasted before\/after, query quality improvements, coverage, and operational time saved.<\/p>\n<\/li>\n<\/ul>\n\n\n\n

          Types of Shared Library<\/h2>\n\n\n\n

          \u201cTypes\u201d vary by platform, but the most useful distinctions are practical rather than theoretical. In SEM \/ Paid Search<\/strong>, Shared Library usage usually falls into these categories:<\/p>\n\n\n\n

          1) Exclusion-focused Shared Library assets<\/h3>\n\n\n\n

          These reduce wasted spend and protect brand integrity:<\/p>\n\n\n\n

            \n
          • Negative keyword lists<\/strong> (for blocking irrelevant queries)<\/li>\n
          • Placement exclusion lists<\/strong> (for display\/video network safety where applicable)<\/li>\n
          • Brand-safety or content exclusion sets<\/strong> (platform dependent)<\/li>\n<\/ul>\n\n\n\n

            2) Targeting-focused Shared Library assets<\/h3>\n\n\n\n

            These support consistent audience strategy in Paid Marketing<\/strong>:<\/p>\n\n\n\n

              \n
            • Remarketing\/audience sets<\/strong> used across campaigns <\/li>\n
            • Customer list segments<\/strong> (where the platform supports shared use and privacy-compliant handling)<\/li>\n<\/ul>\n\n\n\n

              3) Budget and pacing shared controls (platform dependent)<\/h3>\n\n\n\n

              Some platforms allow shared budgets or centralized pacing constructs. Where supported, they help standardize spend allocation across a campaign set\u2014useful in Paid Marketing<\/strong>, but requiring tight oversight.<\/p>\n\n\n\n

              4) Operational and standardization assets<\/h3>\n\n\n\n

              Even when not labeled \u201cShared Library,\u201d many teams treat shared rules, templates, and standardized naming as part of a Shared Library operating model.<\/p>\n\n\n\n

              Real-World Examples of Shared Library<\/h2>\n\n\n\n

              Example 1: Global negative keyword list for lead quality (B2B SaaS)<\/h3>\n\n\n\n

              A B2B company running SEM \/ Paid Search<\/strong> sees spend on job-seeker queries (e.g., \u201ccareers,\u201d \u201csalary,\u201d \u201cinternship\u201d). The team creates a Shared Library negative keyword list called \u201cGlobal \u2013 Employment Intent\u201d and applies it to all non-recruiting campaigns.\nOutcome:<\/strong> Less wasted spend, higher lead quality, and fewer week-to-week firefights in Paid Marketing<\/strong> reporting.<\/p>\n\n\n\n

              Example 2: Brand safety placement exclusions for multi-client agency accounts<\/h3>\n\n\n\n

              An agency manages multiple clients with strict brand guidelines. They build Shared Library placement exclusion lists aligned to each client\u2019s risk tolerance and apply them to all relevant campaigns.\nOutcome:<\/strong> Faster launches, fewer compliance issues, and cleaner governance across Paid Marketing<\/strong> teams\u2014even when account managers change.<\/p>\n\n\n\n

              Example 3: Regional expansion with standardized shared assets (eCommerce)<\/h3>\n\n\n\n

              An eCommerce brand expands to new markets. Instead of recreating exclusions and audience sets for each region, the team uses Shared Library assets as \u201cstarter kits\u201d (global exclusions + region-specific additions).\nOutcome:<\/strong> Launches become repeatable, and SEM \/ Paid Search<\/strong> performance stabilizes faster because foundational controls are consistent.<\/p>\n\n\n\n

              Benefits of Using Shared Library<\/h2>\n\n\n\n

              A well-managed Shared Library<\/strong> creates both performance and operational gains:<\/p>\n\n\n\n

                \n
              • Performance improvements<\/strong>: Fewer irrelevant queries or placements can raise conversion rate and improve efficiency.<\/li>\n
              • Cost savings<\/strong>: Reduced wasted spend from low-intent traffic, especially in competitive SEM \/ Paid Search<\/strong> auctions.<\/li>\n
              • Efficiency gains<\/strong>: One update can improve dozens of campaigns, freeing time for creative testing and strategy.<\/li>\n
              • Better audience experience<\/strong>: More relevant targeting and fewer mismatched ads reduce user frustration and improve brand perception\u2014often overlooked in Paid Marketing<\/strong> discussions.<\/li>\n
              • Easier onboarding<\/strong>: New team members can learn \u201chow we run search\u201d by reviewing Shared Library assets and their documentation.<\/li>\n<\/ul>\n\n\n\n

                Challenges of Shared Library<\/h2>\n\n\n\n

                A Shared Library<\/strong> can also introduce risks if it\u2019s poorly designed or over-centralized:<\/p>\n\n\n\n

                  \n
                • Overblocking and lost volume<\/strong>: Aggressive shared negative lists can suppress valuable traffic across many campaigns.<\/li>\n
                • One change, many consequences<\/strong>: Shared assets amplify impact\u2014good and bad. Without review processes, mistakes scale instantly.<\/li>\n
                • Ownership ambiguity<\/strong>: If nobody \u201cowns\u201d the Shared Library, it becomes cluttered, outdated, or contradictory.<\/li>\n
                • Platform limitations<\/strong>: Not every ad platform supports the same shared objects, and some features behave differently across networks.<\/li>\n
                • Measurement fog<\/strong>: It can be hard to isolate the effect of a single shared list when many variables change in Paid Marketing<\/strong> at once.<\/li>\n<\/ul>\n\n\n\n

                  Best Practices for Shared Library<\/h2>\n\n\n\n

                  To get consistent value from a Shared Library<\/strong>, treat it like a product: defined, maintained, measured, and improved.<\/p>\n\n\n\n

                  Establish clear structure and naming<\/h3>\n\n\n\n

                  Use naming that encodes scope and intent, such as:<\/p>\n\n\n\n

                    \n
                  • Global \u2013 Low Intent Negatives<\/code><\/li>\n
                  • Brand \u2013 Competitor Exclusions<\/code><\/li>\n
                  • Region \u2013 Placement Exclusions \u2013 EMEA<\/code><\/li>\n<\/ul>\n\n\n\n

                    This reduces misapplication in SEM \/ Paid Search<\/strong> accounts with many moving parts.<\/p>\n\n\n\n

                    Separate \u201cglobal\u201d from \u201clocal\u201d<\/h3>\n\n\n\n

                    A practical pattern:<\/p>\n\n\n\n

                      \n
                    • Global list<\/strong>: High-confidence exclusions that are almost always irrelevant.<\/li>\n
                    • Campaign list<\/strong>: Tight exclusions tied to a specific offer or funnel stage.<\/li>\n
                    • Experimental list<\/strong>: New exclusions tested on a subset before broad rollout.<\/li>\n<\/ul>\n\n\n\n

                      Add guardrails and approvals<\/h3>\n\n\n\n

                      For high-impact Shared Library assets:<\/p>\n\n\n\n

                        \n
                      • Require peer review for edits<\/li>\n
                      • Use role-based permissions<\/li>\n
                      • Keep a lightweight change log (what changed, why, when)<\/li>\n<\/ul>\n\n\n\n

                        Review on a schedule tied to spend and volatility<\/h3>\n\n\n\n

                        High-spend Paid Marketing<\/strong> accounts should review shared exclusions frequently. Lower-spend accounts can use a monthly or quarterly cadence. The key is consistency.<\/p>\n\n\n\n

                        Audit for duplication and conflict<\/h3>\n\n\n\n

                        Periodically check for:<\/p>\n\n\n\n

                          \n
                        • Multiple lists that do the same thing<\/li>\n
                        • Contradictory rules<\/li>\n
                        • Lists applied where they shouldn\u2019t be<\/li>\n<\/ul>\n\n\n\n

                          Tools Used for Shared Library<\/h2>\n\n\n\n

                          A Shared Library<\/strong> lives inside ad platforms, but strong programs rely on a broader tool ecosystem to manage, validate, and learn from shared assets in Paid Marketing<\/strong> and SEM \/ Paid Search<\/strong>:<\/p>\n\n\n\n

                            \n
                          • Ad platforms<\/strong>: Where Shared Library assets are created, applied, and permissioned.<\/li>\n
                          • Analytics tools<\/strong>: To evaluate downstream impact (leads, revenue, retention), not just click metrics.<\/li>\n
                          • Tag management and conversion tracking systems<\/strong>: To ensure changes don\u2019t \u201cimprove efficiency\u201d only because measurement broke.<\/li>\n
                          • Automation tools<\/strong>: Rules, scripts, bulk editors, and workflow automation to apply Shared Library updates safely and consistently.<\/li>\n
                          • CRM systems<\/strong>: For lead quality feedback loops (critical in SEM \/ Paid Search<\/strong> lead gen).<\/li>\n
                          • Reporting dashboards \/ BI<\/strong>: To monitor spend, query quality, conversion rates, and anomalies after Shared Library changes.<\/li>\n
                          • Documentation and collaboration tools<\/strong>: To store definitions, owners, and change rationale so knowledge survives team turnover.<\/li>\n<\/ul>\n\n\n\n

                            Metrics Related to Shared Library<\/h2>\n\n\n\n

                            Shared Library success is rarely measured by \u201chow many lists we have.\u201d It\u2019s measured by performance stability, efficiency, and reduced waste.<\/p>\n\n\n\n

                            Useful metrics include:<\/p>\n\n\n\n

                              \n
                            • Wasted spend indicators<\/strong>: Spend on irrelevant queries\/placements before vs after applying shared exclusions.<\/li>\n
                            • Search term quality<\/strong> (for SEM \/ Paid Search<\/strong>): <\/li>\n
                            • Share of queries mapped to high-intent themes <\/li>\n
                            • Reduction in irrelevant query categories over time<\/li>\n
                            • Conversion efficiency<\/strong>: Conversion rate, cost per conversion, and value per click (where applicable).<\/li>\n
                            • Lead quality metrics<\/strong> (for lead gen Paid Marketing<\/strong>): Qualified rate, sales acceptance rate, or pipeline per cost.<\/li>\n
                            • Operational efficiency<\/strong>: Time-to-implement policy changes, number of campaigns updated per hour, or reduction in repetitive edits.<\/li>\n
                            • Error rate \/ rollback frequency<\/strong>: How often Shared Library changes require emergency fixes.<\/li>\n<\/ul>\n\n\n\n

                              Future Trends of Shared Library<\/h2>\n\n\n\n

                              Shared Library capabilities are evolving as platforms push more automation and policy enforcement into Paid Marketing<\/strong> workflows.<\/p>\n\n\n\n

                              What to expect:<\/p>\n\n\n\n

                                \n
                              • AI-assisted list creation and maintenance<\/strong>: Systems may recommend exclusions or shared audience definitions based on performance patterns\u2014useful, but requiring human oversight to avoid overgeneralization.<\/li>\n
                              • More automated governance<\/strong>: Change approvals, anomaly detection, and automatic alerts when Shared Library edits cause sudden performance shifts.<\/li>\n
                              • Greater personalization with privacy constraints<\/strong>: As measurement changes, Shared Library audience strategies will lean more on first-party data and modeled signals while staying privacy-compliant.<\/li>\n
                              • Cross-channel standardization<\/strong>: Teams will increasingly treat Shared Library assets as part of a broader \u201cmarketing standards library,\u201d aligning SEM \/ Paid Search<\/strong> with other Paid Marketing<\/strong> channels using shared definitions and guardrails.<\/li>\n<\/ul>\n\n\n\n

                                Shared Library vs Related Terms<\/h2>\n\n\n\n

                                Understanding nearby concepts helps teams apply a Shared Library<\/strong> correctly.<\/p>\n\n\n\n

                                Shared Library vs campaign-level settings<\/h3>\n\n\n\n

                                Campaign-level settings are local and flexible, but they\u2019re easy to forget and hard to keep consistent. A Shared Library is designed for assets that should be reused and centrally maintained.<\/p>\n\n\n\n

                                Shared Library vs templates<\/h3>\n\n\n\n

                                Templates help you create new campaigns faster, but they don\u2019t automatically update existing campaigns when standards change. Shared Library assets are \u201clive\u201d in the sense that edits can affect all attached campaigns.<\/p>\n\n\n\n

                                Shared Library vs account-wide defaults<\/h3>\n\n\n\n

                                Account defaults apply broadly but can be too blunt. A Shared Library sits in between: more scalable than campaign edits, but more controllable than universal defaults\u2014especially valuable in SEM \/ Paid Search<\/strong> accounts with multiple business lines.<\/p>\n\n\n\n

                                Who Should Learn Shared Library<\/h2>\n\n\n\n

                                Shared Library knowledge pays off across roles:<\/p>\n\n\n\n

                                  \n
                                • Marketers<\/strong>: Build scalable processes for Paid Marketing<\/strong> without sacrificing agility.<\/li>\n
                                • Analysts<\/strong>: Better interpret performance changes when shared assets roll out across campaigns.<\/li>\n
                                • Agencies<\/strong>: Standardize execution across clients while maintaining clear boundaries and approvals.<\/li>\n
                                • Business owners and founders<\/strong>: Reduce risk and dependency on \u201cone expert who knows where everything is.\u201d<\/li>\n
                                • Developers and marketing ops<\/strong>: Support automation, permissions, and data feedback loops that keep Shared Library assets clean and effective.<\/li>\n<\/ul>\n\n\n\n

                                  Summary of Shared Library<\/h2>\n\n\n\n

                                  A Shared Library<\/strong> is a centralized platform area for reusable campaign assets that can be applied across multiple campaigns and maintained consistently. It matters because it reduces wasted effort, enforces standards, and helps teams scale Paid Marketing<\/strong> operations with fewer mistakes. In SEM \/ Paid Search<\/strong>, Shared Library assets commonly support exclusions, targeting consistency, governance, and faster rollouts\u2014turning fragmented account management into a more reliable system.<\/p>\n\n\n\n

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

                                  1) What is a Shared Library used for most often?<\/h3>\n\n\n\n

                                  Most teams use a Shared Library for shared negative keyword lists and other reusable exclusions or audience sets that should stay consistent across multiple campaigns in Paid Marketing<\/strong>.<\/p>\n\n\n\n

                                  2) Can a Shared Library improve SEM \/ Paid Search performance quickly?<\/h3>\n\n\n\n

                                  Yes\u2014especially when it reduces irrelevant traffic at scale. In SEM \/ Paid Search<\/strong>, applying a well-built shared negative list across many campaigns can cut wasted spend quickly, but you should monitor for overblocking.<\/p>\n\n\n\n

                                  3) What should not go into a Shared Library?<\/h3>\n\n\n\n

                                  Avoid adding items that are highly campaign-specific, experimental without a test plan, or likely to change daily. If an asset needs constant tweaking, it may belong at the campaign level until it stabilizes.<\/p>\n\n\n\n

                                  4) How do you prevent Shared Library changes from hurting results?<\/h3>\n\n\n\n

                                  Use permissions, peer review, clear naming, and staged rollouts. Treat Shared Library updates like releases: document the reason, apply to a subset first when risk is high, and watch leading indicators.<\/p>\n\n\n\n

                                  5) How often should Shared Library assets be reviewed?<\/h3>\n\n\n\n

                                  Tie the cadence to spend and volatility. High-spend Paid Marketing<\/strong> and fast-changing SEM \/ Paid Search<\/strong> accounts may review weekly or biweekly; stable programs may review monthly or quarterly.<\/p>\n\n\n\n

                                  6) Is Shared Library only for large accounts?<\/h3>\n\n\n\n

                                  No. Even small advertisers benefit when they run multiple campaigns or offers. A simple Shared Library structure can prevent repeat mistakes and make scaling easier when budgets grow.<\/p>\n\n\n\n

                                  7) How do you measure the impact of a Shared Library change?<\/h3>\n\n\n\n

                                  Track before\/after shifts in wasted spend indicators, conversion efficiency, and lead quality (if applicable). Also measure operational metrics like time saved and the reduction of duplicated campaign edits across Paid Marketing<\/strong> teams.<\/p>\n","protected":false},"excerpt":{"rendered":"

                                  A **Shared Library** is a centralized place inside an ad account (or across connected accounts, depending on the platform) where teams store reusable campaign resources\u2014then apply those resources consistently across multiple campaigns or ad groups. In **Paid Marketing**, it\u2019s one of the most practical ways to reduce repetitive work, prevent mistakes, and enforce standards at scale. In **SEM \/ Paid Search**, where dozens (or thousands) of keywords, audiences, exclusions, and settings can change weekly, a Shared Library helps teams stay aligned without slowing execution.<\/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":[1913],"tags":[],"class_list":["post-11268","post","type-post","status-publish","format-standard","hentry","category-sem-paid-search"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/11268","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=11268"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/11268\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=11268"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=11268"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=11268"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}