{"id":9747,"date":"2026-03-28T09:00:12","date_gmt":"2026-03-28T09:00:12","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/site-query\/"},"modified":"2026-03-28T09:00:12","modified_gmt":"2026-03-28T09:00:12","slug":"site-query","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/site-query\/","title":{"rendered":"Site Query: What It Is, Key Features, Benefits, Use Cases, and How It Fits in SEO"},"content":{"rendered":"\n

A Site Query<\/strong> is one of the simplest, fastest ways to understand how a search engine currently \u201csees\u201d a website. In Organic Marketing<\/strong>, it\u2019s often used as a quick diagnostic to check whether key pages are indexed, which pages appear most prominently, and whether search results reflect your intended brand and content strategy. In SEO<\/strong>, it can highlight technical indexing problems, content duplication signals, and mismatches between what you published and what search engines choose to show.<\/p>\n\n\n\n

Even though a Site Query is not a complete auditing method, it remains a highly practical technique in modern Organic Marketing<\/strong> because it offers immediate directional insight\u2014often before you open a crawl tool, log into analytics, or run a full technical review. Used correctly, it helps teams prioritize investigations, spot anomalies early, and validate whether recent changes appear to be taking effect.<\/p>\n\n\n\n

What Is Site Query?<\/h2>\n\n\n\n

A Site Query<\/strong> is a search operator-based query (commonly using the site:<\/code> operator) that restricts search results to a specific domain, subdomain, or folder. In plain terms: it\u2019s a way to ask a search engine, \u201cShow me what you have indexed for this site.\u201d<\/p>\n\n\n\n

The core concept is straightforward:<\/p>\n\n\n\n

    \n
  • You provide a domain (or section of a site).<\/li>\n
  • The search engine returns results from its index that match that scope.<\/li>\n
  • You can refine the query with additional keywords to find specific page types, topics, or templates.<\/li>\n<\/ul>\n\n\n\n

    From a business perspective, Site Query results act like a quick \u201cvisibility snapshot.\u201d They can surface which pages are being selected for display, whether outdated URLs still appear, and how your site\u2019s content footprint is represented. In Organic Marketing<\/strong>, this helps teams align content production, brand messaging, and conversion paths with what users can actually find.<\/p>\n\n\n\n

    Within SEO<\/strong>, the Site Query is most commonly used to:<\/p>\n\n\n\n

      \n
    • Validate basic indexation presence (at a high level)<\/li>\n
    • Spot suspicious index bloat (too many low-value URLs indexed)<\/li>\n
    • Identify duplicates, parameterized URLs, and legacy paths<\/li>\n
    • Find title\/URL patterns that suggest template problems<\/li>\n<\/ul>\n\n\n\n

      Why Site Query Matters in Organic Marketing<\/h2>\n\n\n\n

      A Site Query matters because Organic Marketing<\/strong> performance depends on discoverability. If important pages aren\u2019t indexed\u2014or if the wrong versions are indexed\u2014your best content may never compete for rankings.<\/p>\n\n\n\n

      Strategically, Site Query usage supports:<\/p>\n\n\n\n

        \n
      • Content governance:<\/strong> Confirm that new hubs, guides, and landing pages are appearing in the index.<\/li>\n
      • Brand control:<\/strong> Identify off-brand titles, outdated messaging, or old subdomains still showing up.<\/li>\n
      • Faster troubleshooting:<\/strong> Spot indexing anomalies quickly after migrations, redesigns, or CMS changes.<\/li>\n
      • Competitive readiness:<\/strong> When you can rapidly validate indexation and footprint, you can adapt campaigns faster.<\/li>\n<\/ul>\n\n\n\n

        The business value is measurable. Better indexation quality improves the odds that your intended pages win impressions and clicks, which translates to stronger pipeline, revenue, or audience growth\u2014especially for content-led Organic Marketing<\/strong> programs.<\/p>\n\n\n\n

        How Site Query Works<\/h2>\n\n\n\n

        A Site Query is simple in form but nuanced in interpretation. In practice, it works like this:<\/p>\n\n\n\n

          \n
        1. \n

          Input (the query you run)<\/strong>\n You enter a scoped query in a search engine, typically:\n – site:example.com<\/code> (entire domain)\n – site:blog.example.com<\/code> (subdomain)\n – site:example.com\/resources\/<\/code> (folder)\n You can add keywords to narrow results (for example, a product name or topic).<\/p>\n<\/li>\n

        2. \n

          Processing (how the engine responds)<\/strong>\n The search engine returns a set of indexed URLs that match your scope and any added terms. These results are influenced by canonicalization, duplicate clustering, quality algorithms, localization, and personalization factors. This is why a Site Query is indicative, not definitive.<\/p>\n<\/li>\n

        3. \n

          Execution (how you analyze it)<\/strong>\n You review:\n – Which pages show up (and which don\u2019t)\n – What titles and snippets look like\n – Whether old URLs or parameter variations appear\n – Whether the visible \u201ccount\u201d seems unusually high or low<\/p>\n<\/li>\n

        4. \n

          Output (the action you take)<\/strong>\n You use the findings to guide next steps in SEO<\/strong> and Organic Marketing<\/strong>, such as:\n – Investigating indexing and crawl controls (robots directives, canonicals, internal linking)\n – Consolidating duplicates\n – Improving content targeting and templates\n – Planning redirects or pruning low-value pages<\/p>\n<\/li>\n<\/ol>\n\n\n\n

          Key Components of Site Query<\/h2>\n\n\n\n

          A Site Query is not a standalone system; it\u2019s a technique. To use it effectively in SEO<\/strong> and Organic Marketing<\/strong>, you need a few supporting components:<\/p>\n\n\n\n

          Data inputs<\/h3>\n\n\n\n
            \n
          • Domain, subdomain, or folder scope<\/strong> you want to evaluate<\/li>\n
          • Keywords or patterns<\/strong> to isolate page types (e.g., \u201cpricing,\u201d \u201clogin,\u201d \u201ctag,\u201d \u201ccategory,\u201d \u201cPDF\u201d)<\/li>\n
          • Known URL samples<\/strong> (important pages, recently launched pages, deprecated pages)<\/li>\n<\/ul>\n\n\n\n

            Processes<\/h3>\n\n\n\n
              \n
            • Baseline checks:<\/strong> Establish what \u201cnormal\u201d looks like for your site footprint.<\/li>\n
            • Change monitoring:<\/strong> Re-run Site Query checks after releases, migrations, or content pushes.<\/li>\n
            • Triage rules:<\/strong> Define what constitutes an incident (e.g., money pages missing, index bloat increases, staging pages appear).<\/li>\n<\/ul>\n\n\n\n

              Systems and responsibilities<\/h3>\n\n\n\n
                \n
              • SEO ownership:<\/strong> Defines query patterns, interprets results, and prioritizes fixes.<\/li>\n
              • Engineering or web team:<\/strong> Implements technical changes (redirects, indexing controls, canonical logic).<\/li>\n
              • Content team:<\/strong> Updates templates, metadata, internal linking, and content strategy based on findings.<\/li>\n<\/ul>\n\n\n\n

                Supporting validation sources (important)<\/h3>\n\n\n\n

                A Site Query should be cross-checked with:\n– Search engine indexing reports (where available)\n– Server logs or crawl data\n– Your internal site search or CMS exports\n– Analytics and landing-page data<\/p>\n\n\n\n

                Types of Site Query<\/h2>\n\n\n\n

                \u201cTypes\u201d of Site Query are less about formal categories and more about common contexts and scopes<\/strong> used in real work:<\/p>\n\n\n\n

                1) Domain-level Site Query<\/h3>\n\n\n\n

                Used to gauge overall index footprint and find broad issues like duplicates, thin pages, or legacy paths.<\/p>\n\n\n\n

                2) Subdomain-level Site Query<\/h3>\n\n\n\n

                Useful when content is split across subdomains (e.g., blog, help center, community). This is common in SaaS Organic Marketing<\/strong> stacks.<\/p>\n\n\n\n

                3) Folder\/path Site Query<\/h3>\n\n\n\n

                Helps validate how a specific section performs in indexation, such as \/blog\/<\/code>, \/resources\/<\/code>, \/products\/<\/code>, or \/locations\/<\/code>.<\/p>\n\n\n\n

                4) Keyword-refined Site Query<\/h3>\n\n\n\n

                Combines scope with a term to locate specific content clusters:\n– Find all indexed pages about a product feature\n– Verify \u201cpricing\u201d pages or \u201ctemplate\u201d pages are handled correctly\n– Identify which pages a search engine associates with a topic<\/p>\n\n\n\n

                5) Quality-control and anomaly Site Query<\/h3>\n\n\n\n

                Used to detect:\n– Staging or development URLs leaking into index\n– Parameter URLs, faceted navigation, and internal search results pages\n– PDFs or other file types that might compete with HTML pages<\/p>\n\n\n\n

                Real-World Examples of Site Query<\/h2>\n\n\n\n

                Example 1: Post-migration indexing validation<\/h3>\n\n\n\n

                A company migrates from \/guides\/<\/code> to \/learn\/<\/code> as part of an Organic Marketing<\/strong> overhaul. A Site Query scoped to the old folder reveals many old URLs still appearing, suggesting redirects may be incomplete or canonicals inconsistent. The SEO<\/strong> team then checks redirect coverage and internal links to ensure the new URLs become the primary indexed versions.<\/p>\n\n\n\n

                Example 2: Diagnosing index bloat from faceted navigation<\/h3>\n\n\n\n

                An ecommerce brand notices performance volatility. A Site Query reveals thousands of indexed URLs with filter parameters and near-duplicate category variants. This insight drives an SEO<\/strong> plan: consolidate or block low-value parameter combinations, strengthen canonical tags, and improve internal linking to key category pages\u2014supporting stronger Organic Marketing<\/strong> visibility for head terms.<\/p>\n\n\n\n

                Example 3: Confirming content cluster coverage for a new product line<\/h3>\n\n\n\n

                A SaaS team publishes a set of comparison and use-case pages. By running Site Query checks with the product name plus modifiers (e.g., \u201cintegrations,\u201d \u201csecurity,\u201d \u201cpricing\u201d), they confirm which pages are indexed and whether titles\/snippets reflect the intended messaging. This supports Organic Marketing<\/strong> alignment between content strategy and real SERP presence.<\/p>\n\n\n\n

                Benefits of Using Site Query<\/h2>\n\n\n\n

                Used appropriately, a Site Query delivers several practical advantages:<\/p>\n\n\n\n

                  \n
                • Faster issue detection:<\/strong> Identify indexing surprises quickly without waiting for full audits.<\/li>\n
                • Higher SEO efficiency:<\/strong> Narrow down where to investigate\u2014templates, sections, or page types.<\/li>\n
                • Better content governance:<\/strong> Catch old, off-topic, or low-quality pages that dilute topical focus.<\/li>\n
                • Improved audience experience:<\/strong> Ensure searchers land on accurate, up-to-date pages rather than legacy or duplicate versions.<\/li>\n
                • Cost savings:<\/strong> Reduce wasted effort by validating assumptions early (e.g., \u201cIs it indexed at all?\u201d) before deeper technical work.<\/li>\n<\/ul>\n\n\n\n

                  For Organic Marketing<\/strong>, these benefits compound over time because indexation quality influences how consistently your content can earn impressions and clicks.<\/p>\n\n\n\n

                  Challenges of Site Query<\/h2>\n\n\n\n

                  A Site Query is useful, but it has real limitations that matter in SEO<\/strong> decision-making:<\/p>\n\n\n\n

                    \n
                  • Result counts are unreliable:<\/strong> The displayed number of results can be approximate and fluctuate.<\/li>\n
                  • Personalization and localization effects:<\/strong> Results can differ by geography, device, and search history.<\/li>\n
                  • Incomplete visibility into indexing state:<\/strong> A URL not appearing doesn\u2019t always mean it isn\u2019t indexed; it may be de-prioritized, clustered, or filtered.<\/li>\n
                  • Misinterpretation risk:<\/strong> Teams may overreact to Site Query observations without confirming via indexing reports, logs, or crawls.<\/li>\n
                  • Not a substitute for auditing:<\/strong> It won\u2019t tell you crawl depth, internal link equity distribution, or rendering problems by itself.<\/li>\n<\/ul>\n\n\n\n

                    In short: Site Query is a directional signal\u2014best for triage and validation, not final conclusions.<\/p>\n\n\n\n

                    Best Practices for Site Query<\/h2>\n\n\n\n

                    To make Site Query a reliable part of your Organic Marketing<\/strong> and SEO<\/strong> workflow:<\/p>\n\n\n\n

                      \n
                    1. \n

                      Define repeatable query patterns<\/strong>\n Keep a documented list of the queries you run (domain, subdomains, folders, and keyword refinements). Consistency improves trend spotting.<\/p>\n<\/li>\n

                    2. \n

                      Pair Site Query with a hypothesis<\/strong>\n Examples:\n – \u201cOur new hub isn\u2019t indexing.\u201d\n – \u201cOld URLs are still showing after redirects.\u201d\n – \u201cFaceted filters are creating duplicates.\u201d<\/p>\n<\/li>\n

                    3. \n

                      Validate with at least one other data source<\/strong>\n Confirm findings using indexing reports, crawl tools, server logs, analytics landing pages, or CMS exports.<\/p>\n<\/li>\n

                    4. \n

                      Segment by templates and intent<\/strong>\n Run checks for page types that often cause issues:\n – Internal search pages\n – Tag\/category archives\n – Pagination\n – Printable pages\n – PDFs versus HTML<\/p>\n<\/li>\n

                    5. \n

                      Use it after every major release<\/strong>\n After migrations, CMS changes, URL structure changes, or large content pushes, run Site Query checks for the affected sections.<\/p>\n<\/li>\n

                    6. \n

                      Turn findings into a prioritized action list<\/strong>\n Focus on impact:\n – Missing revenue pages or lead-gen pages\n – Index bloat harming crawl efficiency\n – Duplicate clusters cannibalizing key topics<\/p>\n<\/li>\n<\/ol>\n\n\n\n

                      Tools Used for Site Query<\/h2>\n\n\n\n

                      A Site Query itself is executed in a search engine interface, but operationalizing it within SEO<\/strong> and Organic Marketing<\/strong> typically involves tool categories that support investigation and measurement:<\/p>\n\n\n\n

                        \n
                      • SEO tools (auditing and crawling):<\/strong> Identify duplicates, canonicals, redirect chains, indexability rules, and internal link patterns that explain Site Query findings.<\/li>\n
                      • Analytics tools:<\/strong> Confirm whether indexed pages are receiving organic sessions, and whether landing-page behavior matches intent.<\/li>\n
                      • Search performance tools:<\/strong> Evaluate impressions, clicks, and query\/page relationships to see if the \u201cright\u201d pages are being surfaced.<\/li>\n
                      • Log analysis tools:<\/strong> Determine how bots crawl the site, which helps explain why certain pages show in Site Query results.<\/li>\n
                      • Reporting dashboards:<\/strong> Track recurring Site Query checks alongside indexing and performance metrics for ongoing Organic Marketing<\/strong> monitoring.<\/li>\n
                      • CMS and site governance workflows:<\/strong> Ensure noindex rules, canonical templates, and redirect mappings are managed consistently across teams.<\/li>\n<\/ul>\n\n\n\n

                        Metrics Related to Site Query<\/h2>\n\n\n\n

                        A Site Query is not a metric by itself, but it points to measurable indicators that matter for SEO<\/strong>:<\/p>\n\n\n\n

                          \n
                        • Indexed page footprint (directional):<\/strong> Whether the apparent number and composition of indexed pages aligns with expectations.<\/li>\n
                        • Indexation rate (validated elsewhere):<\/strong> Proportion of submitted\/known URLs that are indexed.<\/li>\n
                        • Organic landing page distribution:<\/strong> Whether traffic concentrates on intended pages or leaks to duplicates\/legacy URLs.<\/li>\n
                        • Crawl efficiency signals:<\/strong> Frequency and volume of bot hits to low-value URLs (from logs), often correlated with index bloat suggested by Site Query.<\/li>\n
                        • SERP snippet quality:<\/strong> Consistency of titles and descriptions shown, which affects click-through behavior.<\/li>\n
                        • Cannibalization indicators:<\/strong> Multiple similar pages appearing for the same topic within the same site scope.<\/li>\n<\/ul>\n\n\n\n

                          Future Trends of Site Query<\/h2>\n\n\n\n

                          Site Query usage is evolving alongside changes in search ecosystems and Organic Marketing<\/strong> operations:<\/p>\n\n\n\n

                            \n
                          • AI-assisted diagnostics:<\/strong> Teams increasingly use automation to flag anomalies (e.g., sudden appearance of parameter URLs) and suggest likely causes.<\/li>\n
                          • More emphasis on quality and intent:<\/strong> Search engines continue to cluster duplicates and de-emphasize thin pages, making Site Query interpretation more about \u201cwhich pages are selected\u201d than raw counts.<\/li>\n
                          • Richer indexing controls:<\/strong> Better template-level governance (canonicals, structured data, indexing directives) will reduce the gap between what\u2019s published and what appears in Site Query results.<\/li>\n
                          • Privacy and measurement shifts:<\/strong> As attribution gets harder, technical SEO<\/strong> signals (indexation quality, crawl efficiency) become more important operational KPIs for Organic Marketing<\/strong> teams.<\/li>\n
                          • Content consolidation strategies:<\/strong> Brands will increasingly prune, merge, and strengthen content hubs\u2014Site Query checks help validate that consolidation is reflected in what search engines surface.<\/li>\n<\/ul>\n\n\n\n

                            Site Query vs Related Terms<\/h2>\n\n\n\n

                            Site Query vs Index Coverage (indexing reports)<\/h3>\n\n\n\n

                            A Site Query is an external, SERP-based snapshot of what appears indexed and retrievable. Index coverage reporting (where available) is a more direct view of indexing states and reasons (excluded, crawled but not indexed, etc.). In SEO<\/strong>, use Site Query for quick discovery and coverage reports for confirmation and root-cause analysis.<\/p>\n\n\n\n

                            Site Query vs Crawl (site crawling)<\/h3>\n\n\n\n

                            A crawl tool shows what a bot can<\/em> access and how the site is built (links, status codes, canonicals, directives). A Site Query shows what a search engine chose<\/em> to index and display. Both are essential in Organic Marketing<\/strong>: crawling finds technical causes; Site Query reflects real-world SERP representation.<\/p>\n\n\n\n

                            Site Query vs \u201cGoogle dorking\u201d \/ advanced operators<\/h3>\n\n\n\n

                            A Site Query is one operator pattern focused on scope. Advanced operator use can include many refinements to find sensitive files, duplicates, or patterns. In an SEO<\/strong> context, keep operator usage ethical and focused on your own properties and legitimate QA.<\/p>\n\n\n\n

                            Who Should Learn Site Query<\/h2>\n\n\n\n
                              \n
                            • Marketers:<\/strong> To verify that campaign assets and content hubs are discoverable and represented correctly in search.<\/li>\n
                            • Analysts:<\/strong> To triangulate performance changes with indexation and SERP visibility shifts in Organic Marketing<\/strong>.<\/li>\n
                            • Agencies:<\/strong> To speed up audits, spot red flags early, and communicate issues clearly to clients.<\/li>\n
                            • Business owners and founders:<\/strong> To understand whether the site\u2019s most important pages are actually findable, supporting sustainable SEO<\/strong> growth.<\/li>\n
                            • Developers:<\/strong> To validate the impact of releases (redirects, canonical logic, robots directives) and reduce indexing regressions.<\/li>\n<\/ul>\n\n\n\n

                              Summary of Site Query<\/h2>\n\n\n\n

                              A Site Query<\/strong> is a scoped search operator technique used to see which pages from a domain, subdomain, or folder appear in a search engine\u2019s index. It matters because Organic Marketing<\/strong> depends on discoverability, and Site Query checks can quickly reveal missing pages, duplicates, index bloat, or legacy URLs that weaken performance. While it isn\u2019t a complete audit method, it\u2019s a powerful triage tool that complements technical investigation and supports better SEO<\/strong> outcomes through faster validation and smarter prioritization.<\/p>\n\n\n\n

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

                              1) What is a Site Query used for?<\/h3>\n\n\n\n

                              A Site Query is used to quickly inspect which pages from a site appear indexed and visible in search results. It\u2019s commonly used for fast troubleshooting and content governance in SEO<\/strong> and Organic Marketing<\/strong> workflows.<\/p>\n\n\n\n

                              2) Does a Site Query show every page that is indexed?<\/h3>\n\n\n\n

                              Not necessarily. Site Query results can be incomplete or clustered due to duplication handling, quality filtering, localization, and other ranking systems. Treat it as a directional view and confirm with indexing reports and crawl data.<\/p>\n\n\n\n

                              3) Why are some important pages missing from my Site Query results?<\/h3>\n\n\n\n

                              Common causes include weak internal linking, accidental noindex directives, canonical tags pointing elsewhere, redirects, rendering issues, or the search engine deciding other pages better satisfy the query. Validate by checking the URL directly, reviewing indexing signals, and using technical SEO<\/strong> diagnostics.<\/p>\n\n\n\n

                              4) How often should I run Site Query checks for SEO?<\/h3>\n\n\n\n

                              Run Site Query checks after major site changes (migrations, redesigns, CMS template updates), after large content releases, and during performance anomalies. Many teams also include lightweight checks as part of routine Organic Marketing<\/strong> QA.<\/p>\n\n\n\n

                              5) Can Site Query help detect duplicate content or index bloat?<\/h3>\n\n\n\n

                              Yes. A Site Query can reveal repeated URL patterns, parameterized URLs, and multiple near-identical pages being indexed. It won\u2019t diagnose the root cause alone, but it\u2019s a strong early signal for SEO<\/strong> cleanup work.<\/p>\n\n\n\n

                              6) Is a Site Query a replacement for a full technical audit?<\/h3>\n\n\n\n

                              No. A full audit uses crawls, logs, performance data, and indexing reports to identify causes and quantify impact. Site Query is best for quick discovery, spot checks, and prioritizing where to investigate.<\/p>\n\n\n\n

                              7) How does Site Query support Organic Marketing strategy beyond technical SEO?<\/h3>\n\n\n\n

                              It helps ensure content strategy matches real visibility: the right pages appear for branded and topical checks, legacy content doesn\u2019t overshadow new messaging, and your discoverability aligns with campaign priorities\u2014making Organic Marketing<\/strong> execution more reliable.<\/p>\n","protected":false},"excerpt":{"rendered":"

                              A **Site Query** is one of the simplest, fastest ways to understand how a search engine currently \u201csees\u201d a website. In **Organic Marketing**, it\u2019s often used as a quick diagnostic to check whether key pages are indexed, which pages appear most prominently, and whether search results reflect your intended brand and content strategy. In **SEO**, it can highlight technical indexing problems, content duplication signals, and mismatches between what you published and what search engines choose to show.<\/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":[131],"tags":[],"class_list":["post-9747","post","type-post","status-publish","format-standard","hentry","category-seo"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/9747","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=9747"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/9747\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=9747"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=9747"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=9747"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}