{"id":8799,"date":"2026-03-26T19:15:46","date_gmt":"2026-03-26T19:15:46","guid":{"rendered":"https:\/\/www.wizbrand.com\/tutorials\/community-naming-convention\/"},"modified":"2026-03-26T19:15:46","modified_gmt":"2026-03-26T19:15:46","slug":"community-naming-convention","status":"publish","type":"post","link":"https:\/\/www.wizbrand.com\/tutorials\/community-naming-convention\/","title":{"rendered":"Community Naming Convention: What It Is, Key Features, Benefits, Use Cases, and How It Fits in Community Marketing"},"content":{"rendered":"\n

A Community Naming Convention<\/strong> is a documented, repeatable way to name the spaces, programs, roles, and assets that make up your community ecosystem\u2014everything from forum categories and Discord channels to membership tiers, event series, ambassador programs, and content tags. In Organic Marketing<\/strong>, where growth depends on discoverability, trust, and consistent experiences rather than paid reach, a Community Naming Convention becomes a quiet but powerful lever: it helps people find the right place, understand what it\u2019s for, and participate with confidence.<\/p>\n\n\n\n

In Community Marketing<\/strong>, naming is not just \u201clabels.\u201d Names shape perception, set expectations, improve navigation, and create a shared language between members and your internal teams. A strong Community Naming Convention also reduces operational friction: it streamlines onboarding, reporting, moderation, content planning, and cross-channel measurement\u2014making your community easier to scale without losing clarity.<\/p>\n\n\n\n

What Is Community Naming Convention?<\/h2>\n\n\n\n

A Community Naming Convention<\/strong> is a standardized set of rules that defines how you name community-related elements consistently across platforms and time. It covers both structure<\/strong> (what things are called and how they\u2019re grouped) and syntax<\/strong> (how names are formatted, such as capitalization, prefixes, separators, and tagging).<\/p>\n\n\n\n

At a beginner level, you can think of it as a \u201cstyle guide for your community.\u201d But the business meaning goes further:<\/p>\n\n\n\n

    \n
  • It creates a consistent member experience across channels (forum, social, product community, events).<\/li>\n
  • It reduces confusion and support load by making destinations and purposes obvious.<\/li>\n
  • It makes reporting possible at scale by ensuring the same concept isn\u2019t tracked under five different names.<\/li>\n<\/ul>\n\n\n\n

    In Organic Marketing<\/strong>, Community Naming Convention supports long-term compounding outcomes: better SEO signals from well-structured community content, improved internal linking and topic clustering, higher engagement from reduced friction, and stronger brand recall. Inside Community Marketing<\/strong>, it becomes foundational governance\u2014similar to how campaign naming conventions enable reliable attribution in analytics.<\/p>\n\n\n\n

    Why Community Naming Convention Matters in Organic Marketing<\/h2>\n\n\n\n

    A Community Naming Convention directly affects outcomes that Organic Marketing teams care about:<\/p>\n\n\n\n

    1) Discoverability and navigation<\/strong>\nClear names help members self-serve. If people can\u2019t quickly find \u201cGetting Started,\u201d \u201cProduct Q&A,\u201d or \u201cLocal Meetups,\u201d they leave or ask repetitive questions. Better information scent (clear cues) increases participation and retention.<\/p>\n\n\n\n

    2) Brand consistency and trust<\/strong>\nNaming is branding in action. Consistent, respectful, inclusive naming signals professionalism and safety\u2014key ingredients in community trust, which is a core engine of Organic Marketing.<\/p>\n\n\n\n

    3) Scalable content and SEO benefits<\/strong>\nCommunities generate user-led content that can rank and bring in new visitors. When categories, tags, and threads follow a Community Naming Convention, you reduce duplication and improve topical organization\u2014helping search engines and humans understand the site.<\/p>\n\n\n\n

    4) Better measurement and operational alignment<\/strong>\nCommunity Marketing often spans product, support, and marketing. A shared naming system reduces ambiguity (\u201cIs \u2018Power Users\u2019 the same as \u2018Champions\u2019?\u201d), enabling cleaner dashboards and more consistent experimentation.<\/p>\n\n\n\n

    5) Competitive advantage<\/strong>\nMany competitors build communities but fail to maintain clarity as they scale. A strong Community Naming Convention is a defensible advantage: it makes your community easier to use, easier to manage, and easier to grow organically.<\/p>\n\n\n\n

    How Community Naming Convention Works<\/h2>\n\n\n\n

    Community Naming Convention is partly procedural and partly governance. In practice, it works like a cycle:<\/p>\n\n\n\n

    1) Inputs \/ triggers<\/strong>\nYou add a new channel, launch a program (e.g., ambassadors), expand to new regions, ship new product features, or see recurring confusion in member questions.<\/p>\n\n\n\n

    2) Analysis and decision-making<\/strong>\nYou audit existing names, map them to user needs and journeys, and align on taxonomy: topics, roles, and purposes. You also consider search behavior (internal search terms and external SEO queries) and brand voice.<\/p>\n\n\n\n

    3) Execution \/ application<\/strong>\nYou apply the Community Naming Convention across:\n– Community architecture (categories, channels, groups)\n– Content templates (event titles, post prefixes, series names)\n– Programs (membership levels, councils, cohorts)\n– Governance artifacts (moderation queues, internal labels)\n– Analytics dimensions (tracking group names, tags, UTM-like community labels where relevant)<\/p>\n\n\n\n

    4) Outputs \/ outcomes<\/strong>\nMembers find the right place faster, engagement becomes more intentional, duplication drops, moderation gets easier, and reporting becomes reliable. Over time, this improves Organic Marketing performance through stronger retention, more referrals, and better compounding content value.<\/p>\n\n\n\n

    Key Components of Community Naming Convention<\/h2>\n\n\n\n

    A robust Community Naming Convention usually includes:<\/p>\n\n\n\n

    Naming rules and syntax<\/h3>\n\n\n\n
      \n
    • Capitalization and punctuation standards <\/li>\n
    • Prefixes\/suffixes (e.g., \u201cAsk:\u201d for Q&A threads, \u201cHow-to:\u201d for tutorials) <\/li>\n
    • Character limits (important for mobile UIs) <\/li>\n
    • Emoji usage policy (if any) and accessibility considerations <\/li>\n<\/ul>\n\n\n\n

      Taxonomy and information architecture<\/h3>\n\n\n\n
        \n
      • Category\/channel hierarchy (top-level vs sub-level) <\/li>\n
      • Tagging strategy (topics, industries, use cases, regions) <\/li>\n
      • Canonical names for recurring concepts (product modules, persona names)<\/li>\n<\/ul>\n\n\n\n

        Governance and responsibilities<\/h3>\n\n\n\n
          \n
        • Who can create new names (admins only vs delegated owners) <\/li>\n
        • Review\/approval process for new channels and programs <\/li>\n
        • Version control and documentation ownership (community ops, marketing ops, or both)<\/li>\n<\/ul>\n\n\n\n

          Data inputs and feedback loops<\/h3>\n\n\n\n
            \n
          • Internal search logs and \u201cno results\u201d queries <\/li>\n
          • Most common support tickets and repeated questions <\/li>\n
          • Member surveys about findability and clarity <\/li>\n
          • SEO insights (topic demand, keyword variants, intent)<\/li>\n<\/ul>\n\n\n\n

            Metrics and reporting alignment<\/h3>\n\n\n\n
              \n
            • A naming-to-reporting mapping so dashboards stay consistent <\/li>\n
            • Guidelines for merging\/renaming without losing historical comparability <\/li>\n<\/ul>\n\n\n\n

              Types of Community Naming Convention<\/h2>\n\n\n\n

              There aren\u2019t universal \u201cofficial types,\u201d but in real Community Marketing work, the most useful distinctions are contextual:<\/p>\n\n\n\n

              1) Structural naming conventions (spaces and containers)<\/h3>\n\n\n\n

              How you name:\n– Categories, channels, groups, rooms, collections\n– Regional chapters or local meetups\n– Private vs public areas <\/p>\n\n\n\n

              Goal: make the community navigable and intuitive.<\/p>\n\n\n\n

              2) Content naming conventions (posts and series)<\/h3>\n\n\n\n

              How you name:\n– Recurring event titles and episode series\n– Post title patterns and prefixes\n– Editorial labels and content tags <\/p>\n\n\n\n

              Goal: increase consistency, scannability, and searchability\u2014key for Organic Marketing.<\/p>\n\n\n\n

              3) Program and role naming conventions (people and participation)<\/h3>\n\n\n\n

              How you name:\n– Ambassador programs, councils, moderators\n– Member tiers, badges, certifications\n– Cohorts and mentorship tracks <\/p>\n\n\n\n

              Goal: set expectations and reduce ambiguity around privileges and responsibilities.<\/p>\n\n\n\n

              4) Internal operational naming conventions (workflows and analytics)<\/h3>\n\n\n\n

              How you name:\n– Moderation queues, internal labels, playbooks\n– Reporting segments and lifecycle stages <\/p>\n\n\n\n

              Goal: ensure measurement and operations scale cleanly.<\/p>\n\n\n\n

              Real-World Examples of Community Naming Convention<\/h2>\n\n\n\n

              Example 1: SaaS product community scaling categories<\/h3>\n\n\n\n

              A SaaS company grows from one product to multiple modules. Without a Community Naming Convention, categories become a mix of feature names, team names, and vague labels (\u201cTips,\u201d \u201cHelp,\u201d \u201cAdvanced\u201d).<\/p>\n\n\n\n

              Implementation scenario:\n– Top-level categories use member intent: Get Started<\/strong>, Product Q&A<\/strong>, How-to Library<\/strong>, Bug Reports<\/strong>, Feature Requests<\/strong>\n– Subcategories use consistent module names aligned with product navigation\n– Tags capture industries and use cases<\/p>\n\n\n\n

              Outcome:\n– Reduced duplicate threads, faster self-service, and better SEO performance from clearer topic clustering\u2014supporting Organic Marketing growth.<\/p>\n\n\n\n

              Example 2: Discord community with consistent channel prefixes<\/h3>\n\n\n\n

              A brand runs a Discord for creators. Channels were created ad hoc, leading to clutter and low participation.<\/p>\n\n\n\n

              Community Naming Convention applied:\n– Prefixes based on purpose: #start-here<\/code>, #ask-<\/code>, #share-<\/code>, #events-<\/code>, #local-<\/code>\n– Weekly events named as a series: \u201cCreator Clinic \u2014 Week ##\u201d\n– Clear \u201cread-only\u201d announcements naming<\/p>\n\n\n\n

              Outcome:\n– Members understand where to post instantly, moderation time decreases, and engagement rises\u2014improving Community Marketing efficiency.<\/p>\n\n\n\n

              Example 3: Global community chapters and event naming<\/h3>\n\n\n\n

              A company launches regional chapters. Without naming standards, events vary wildly (\u201cNYC Meetup,\u201d \u201cNew York Users Group,\u201d \u201cNY Session\u201d).<\/p>\n\n\n\n

              Community Naming Convention applied:\n– Chapter format: City \u2014 Brand Community<\/code>\n– Event format: City | Topic | Month YYYY<\/code>\n– Speaker\/session format: Talk Title (Level: Beginner\/Intermediate\/Advanced)<\/code><\/p>\n\n\n\n

              Outcome:\n– Easier cross-region reporting, consistent brand experience, and improved event discovery through Organic Marketing channels like email, community search, and content reuse.<\/p>\n\n\n\n

              Benefits of Using Community Naming Convention<\/h2>\n\n\n\n

              A well-run Community Naming Convention delivers practical benefits:<\/p>\n\n\n\n

                \n
              • Higher engagement through reduced friction:<\/strong> members find the right place, faster. <\/li>\n
              • Better onboarding and retention:<\/strong> newcomers understand where to start and what\u2019s expected. <\/li>\n
              • Operational efficiency:<\/strong> fewer misrouted posts, less manual moderation, cleaner handoffs. <\/li>\n
              • Improved analytics quality:<\/strong> consistent segments and labels enable trustworthy reporting. <\/li>\n
              • Faster scaling:<\/strong> new chapters, channels, and programs can be launched without chaos. <\/li>\n
              • Stronger brand clarity:<\/strong> consistent naming reinforces positioning and voice. <\/li>\n
              • Compounding Organic Marketing value:<\/strong> well-structured community content becomes easier to discover, reuse, and rank over time.<\/li>\n<\/ul>\n\n\n\n

                Challenges of Community Naming Convention<\/h2>\n\n\n\n

                Community Naming Convention sounds simple, but common pitfalls include:<\/p>\n\n\n\n

                  \n
                • Legacy sprawl:<\/strong> older channels and categories resist renaming because members are used to them. <\/li>\n
                • Cross-platform differences:<\/strong> what works in a forum taxonomy may not fit Slack\/Discord constraints. <\/li>\n
                • Internal politics and ownership:<\/strong> product, support, and marketing may disagree on terminology. <\/li>\n
                • Over-standardization:<\/strong> overly rigid rules can make the community feel bureaucratic or unwelcoming. <\/li>\n
                • Measurement discontinuity:<\/strong> renaming can break trend lines unless you manage reporting mappings. <\/li>\n
                • Localization complexity:<\/strong> global communities need naming that respects language, region, and cultural nuance without fragmenting the brand.<\/li>\n<\/ul>\n\n\n\n

                  Best Practices for Community Naming Convention<\/h2>\n\n\n\n

                  Build from member intent, not internal org charts<\/h3>\n\n\n\n

                  Name spaces for what members want to do: ask, learn, share, meet, troubleshoot. Avoid naming categories after internal teams unless it clearly matches member mental models.<\/p>\n\n\n\n

                  Create a small, memorable hierarchy<\/h3>\n\n\n\n

                  Most communities work best with fewer top-level containers and strong tagging underneath. Excessive categories increase confusion and reduce posting confidence.<\/p>\n\n\n\n

                  Define \u201cwhen to create a new channel\/category\u201d<\/h3>\n\n\n\n

                  Set clear thresholds, such as:\n– Sustained volume (e.g., X posts per week for Y weeks)\n– Distinct audience and intent\n– Clear moderation ownership\n– Measurable purpose tied to Community Marketing goals<\/p>\n\n\n\n

                  Write a living naming playbook<\/h3>\n\n\n\n

                  Include:\n– Examples of good vs bad names\n– Templates for events, chapters, content series\n– Rules for abbreviations, product naming, and inclusive language\n– A change log and deprecation process<\/p>\n\n\n\n

                  Plan for renames with redirects and communication<\/h3>\n\n\n\n

                  Treat renaming like a migration:\n– Announce why it\u2019s changing\n– Provide \u201cold name \u2192 new name\u201d mapping\n– Pin guidance for a transition period\n– Align analytics to preserve historical comparisons<\/p>\n\n\n\n

                  Test with real users and moderators<\/h3>\n\n\n\n

                  Before rolling out a major Community Naming Convention update, test with:\n– New members (findability)\n– Power users (mental model alignment)\n– Moderators (workflow impact)<\/p>\n\n\n\n

                  Tools Used for Community Naming Convention<\/h2>\n\n\n\n

                  Community Naming Convention is operationalized through systems more than single-purpose tools. Common tool groups in Organic Marketing and Community Marketing include:<\/p>\n\n\n\n

                    \n
                  • Community platforms and moderation systems:<\/strong> where categories, tags, and roles are configured and enforced. <\/li>\n
                  • Documentation and knowledge management tools:<\/strong> for the naming playbook, templates, and governance. <\/li>\n
                  • Analytics tools:<\/strong> to measure search terms, engagement by category, retention cohorts, and content performance. <\/li>\n
                  • CRM systems:<\/strong> to align community segments (e.g., champions, advocates) with lifecycle stages and communications. <\/li>\n
                  • SEO tools:<\/strong> to research topic demand and identify terminology members actually use, informing category and tag names. <\/li>\n
                  • Reporting dashboards \/ BI:<\/strong> to standardize naming in dimensions, ensure consistent rollups, and maintain historical mapping after renames. <\/li>\n
                  • Automation tools:<\/strong> to apply labels, route posts, or trigger workflows based on tags and categories\u2014only reliable when naming is consistent.<\/li>\n<\/ul>\n\n\n\n

                    Metrics Related to Community Naming Convention<\/h2>\n\n\n\n

                    Because Community Naming Convention affects clarity and findability, relevant metrics span engagement, efficiency, and brand quality:<\/p>\n\n\n\n

                    Engagement and experience<\/h3>\n\n\n\n
                      \n
                    • Time to first meaningful action (first post, reply, RSVP) <\/li>\n
                    • New member activation rate <\/li>\n
                    • Participation rate by category\/channel <\/li>\n
                    • Internal search success rate (searches that lead to a click or solved outcome) <\/li>\n
                    • Content reuse rate (threads referenced, bookmarked, or linked internally)<\/li>\n<\/ul>\n\n\n\n

                      Operational efficiency<\/h3>\n\n\n\n
                        \n
                      • Moderator touches per post (or moderation time per week) <\/li>\n
                      • Duplicate thread rate (same question posted multiple times) <\/li>\n
                      • Mispost rate (posts moved to other categories) <\/li>\n
                      • Resolution time for questions (especially in support-like spaces)<\/li>\n<\/ul>\n\n\n\n

                        Organic Marketing outcomes<\/h3>\n\n\n\n
                          \n
                        • Growth in organic sign-ups driven by community content <\/li>\n
                        • Non-paid traffic to community pages (where applicable) <\/li>\n
                        • Ranking coverage across core topics (topic depth and breadth) <\/li>\n
                        • Referral and word-of-mouth indicators (mentions, invitations, shared links)<\/li>\n<\/ul>\n\n\n\n

                          Brand and quality signals<\/h3>\n\n\n\n
                            \n
                          • Member satisfaction related to navigation and clarity (survey items) <\/li>\n
                          • Sentiment trends around \u201cconfusing,\u201d \u201chard to find,\u201d \u201cnot sure where to post\u201d <\/li>\n
                          • Consistency audits (percentage of assets following the standard)<\/li>\n<\/ul>\n\n\n\n

                            Future Trends of Community Naming Convention<\/h2>\n\n\n\n

                            Several shifts are shaping how Community Naming Convention evolves within Organic Marketing:<\/p>\n\n\n\n

                              \n
                            • AI-assisted taxonomy management:<\/strong> AI can suggest tags, detect duplicates, and recommend renames based on content similarity\u2014useful, but it still needs governance to avoid drifting terminology. <\/li>\n
                            • Personalized navigation:<\/strong> communities increasingly show different spaces to different members. Naming must remain clear even when the hierarchy is partially hidden or personalized. <\/li>\n
                            • Search-first communities:<\/strong> as internal search improves, naming and tagging strategies become more important than deep hierarchies. <\/li>\n
                            • Privacy and measurement constraints:<\/strong> with tighter privacy expectations, teams may rely more on aggregated behavior metrics. Consistent naming becomes essential for accurate rollups without invasive tracking. <\/li>\n
                            • Cross-channel community ecosystems:<\/strong> Community Marketing often spans community platform, social groups, events, and product experiences. A Community Naming Convention increasingly acts as the \u201cglue\u201d that keeps these consistent.<\/li>\n<\/ul>\n\n\n\n

                              Community Naming Convention vs Related Terms<\/h2>\n\n\n\n

                              Community Naming Convention vs Taxonomy<\/h3>\n\n\n\n
                                \n
                              • Taxonomy<\/strong> is the overall classification system (categories, tags, hierarchy). <\/li>\n
                              • Community Naming Convention<\/strong> is the rule set for how you label and format the taxonomy elements consistently.\nTaxonomy answers \u201cwhat buckets exist?\u201d Naming convention answers \u201cwhat do we call them and how?\u201d<\/li>\n<\/ul>\n\n\n\n

                                Community Naming Convention vs Brand Voice Guidelines<\/h3>\n\n\n\n
                                  \n
                                • Brand voice guidelines<\/strong> define tone, personality, and messaging style. <\/li>\n
                                • Community Naming Convention<\/strong> focuses on operational labels and structural clarity (channels, programs, roles).\nThey should align, but naming convention is more functional and governance-driven.<\/li>\n<\/ul>\n\n\n\n

                                  Community Naming Convention vs Campaign Naming Convention<\/h3>\n\n\n\n
                                    \n
                                  • Campaign naming<\/strong> standardizes marketing initiatives for attribution and reporting. <\/li>\n
                                  • Community Naming Convention<\/strong> standardizes community spaces and programs for usability and measurement.\nBoth serve consistency and analytics, but community naming directly shapes member behavior and experience.<\/li>\n<\/ul>\n\n\n\n

                                    Who Should Learn Community Naming Convention<\/h2>\n\n\n\n
                                      \n
                                    • Marketers:<\/strong> to improve Organic Marketing outcomes through clearer journeys, stronger community-driven content, and more consistent brand experiences. <\/li>\n
                                    • Analysts:<\/strong> to ensure reliable segmentation, reporting, and trend analysis across community initiatives. <\/li>\n
                                    • Agencies and consultants:<\/strong> to build scalable Community Marketing foundations for clients and reduce long-term operational debt. <\/li>\n
                                    • Business owners and founders:<\/strong> to make the community a durable asset rather than a messy collection of channels. <\/li>\n
                                    • Developers and product teams:<\/strong> to align product terminology, in-app community entry points, and metadata for search and personalization.<\/li>\n<\/ul>\n\n\n\n

                                      Summary of Community Naming Convention<\/h2>\n\n\n\n

                                      A Community Naming Convention<\/strong> is a standardized system for naming community spaces, content, roles, and programs. It matters because naming directly influences findability, participation, brand trust, and measurement. Within Organic Marketing<\/strong>, it supports compounding growth by improving discoverability and the long-term value of community-generated content. Within Community Marketing<\/strong>, it provides the governance layer that keeps the community scalable, navigable, and measurable as programs expand.<\/p>\n\n\n\n

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

                                      What is a Community Naming Convention, in simple terms?<\/h3>\n\n\n\n

                                      A Community Naming Convention is a set of rules for naming community categories, channels, programs, roles, and recurring content so members and teams can understand and manage the community consistently.<\/p>\n\n\n\n

                                      How does Community Naming Convention improve Organic Marketing results?<\/h3>\n\n\n\n

                                      It improves navigation and content organization, which increases engagement and retention. Over time, clearer structure also helps community content perform better in search and makes it easier to reuse content across Organic Marketing channels.<\/p>\n\n\n\n

                                      Is Community Naming Convention part of Community Marketing or community operations?<\/h3>\n\n\n\n

                                      It\u2019s both. In Community Marketing, naming shapes campaigns, programs, and member experience. In community operations, it enables scalable moderation, analytics, and governance.<\/p>\n\n\n\n

                                      Should we name community categories after product features or member use cases?<\/h3>\n\n\n\n

                                      Prefer member use cases and intent for top-level categories (Ask, Learn, Share). Use product features as subcategories or tags when they help members find specific answers\u2014this balance usually performs best for Organic Marketing and usability.<\/p>\n\n\n\n

                                      How often should we review our Community Naming Convention?<\/h3>\n\n\n\n

                                      Review quarterly for fast-growing communities and at least twice a year for mature communities. Also review whenever you add major products, expand regions, or see repeated confusion in search logs and support questions.<\/p>\n\n\n\n

                                      What\u2019s the biggest mistake teams make with community naming?<\/h3>\n\n\n\n

                                      Creating too many categories or inconsistent labels that reflect internal teams rather than member needs. This increases confusion, duplicates, and moderation workload\u2014hurting Community Marketing efficiency.<\/p>\n\n\n\n

                                      How do we rename channels or categories without upsetting members?<\/h3>\n\n\n\n

                                      Communicate the reason, provide an \u201cold name \u2192 new name\u201d mapping, keep guidance pinned during a transition period, and ensure analytics\/reporting can still roll up historical data after the change.<\/p>\n","protected":false},"excerpt":{"rendered":"

                                      A **Community Naming Convention** is a documented, repeatable way to name the spaces, programs, roles, and assets that make up your community ecosystem\u2014everything from forum categories and Discord channels to membership tiers, event series, ambassador programs, and content tags. In **Organic Marketing**, where growth depends on discoverability, trust, and consistent experiences rather than paid reach, a Community Naming Convention becomes a quiet but powerful lever: it helps people find the right place, understand what it\u2019s for, and participate with confidence.<\/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":[1901],"tags":[],"class_list":["post-8799","post","type-post","status-publish","format-standard","hentry","category-community-marketing"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/8799","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=8799"}],"version-history":[{"count":0,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/posts\/8799\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/media?parent=8799"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/categories?post=8799"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wizbrand.com\/tutorials\/wp-json\/wp\/v2\/tags?post=8799"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}