{"id":1432,"date":"2026-07-20T06:56:27","date_gmt":"2026-07-20T06:56:27","guid":{"rendered":"https:\/\/maxaeo.ai\/blog\/business-directories-ai-search\/"},"modified":"2026-07-20T06:56:27","modified_gmt":"2026-07-20T06:56:27","slug":"business-directories-ai-search","status":"publish","type":"post","link":"https:\/\/maxaeo.ai\/blog\/business-directories-ai-search\/","title":{"rendered":"Business Directories for AI Search: Which Ones AI Actually Uses"},"content":{"rendered":"<p><strong>Business directories for AI search are the structured databases \u2014 Crunchbase, G2, Wikidata, Capterra, LinkedIn and vertical catalogs \u2014 that ChatGPT, Perplexity, Gemini and Google&#39;s AI answers read to confirm who a company is and decide whether to recommend it.<\/strong> Getting listed accurately in the right ones, and keeping those records current, is now one of the highest-use moves in answer engine optimization. Most guides stop at &quot;keep your NAP consistent.&quot; That is table stakes. This piece goes further: which databases actually feed AI answers, <em>why<\/em> an engine reaches for a directory in the first place, a tiering framework we use when auditing brands, and the maintenance discipline that keeps you cited instead of quietly dropped.<\/p>\n<p>The stakes are simple. When a buyer asks an assistant &quot;what are the best tools for X,&quot; the model assembles a shortlist from the sources it trusts. If your entity is thin, contradicted, or stale across those sources, you are not on the list \u2014 and you never see the query.<\/p>\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" style=\"max-width:100%;height:auto\" loading=\"lazy\"  src=\"https:\/\/maxaeo.ai\/blog\/wp-content\/uploads\/2026\/07\/1784286455764-13-55777-1.jpg\" alt=\"Diagram of business directories for AI search feeding brand facts into ChatGPT, Perplexity and Gemini answers\"><\/figure>\n<h2>What are business directories for AI search?<\/h2>\n<p><strong>Business directories for AI search are third-party, structured data sources that describe companies in a machine-readable, consistent format \u2014 name, category, description, founding date, funding, location, reviews and links \u2014 which large language models use as ground truth when answering questions about brands.<\/strong> They differ from a marketing website in one decisive way: they are <em>independent<\/em>. An AI engine treats a claim you make about yourself with less confidence than the same claim confirmed by an outside catalog.<\/p>\n<p>Think of them as the reference layer of the web. Your site says what you <em>want<\/em> to be true; directories say what the market <em>records<\/em> as true. When the two agree, models cite you more readily. When they disagree, the model hedges \u2014 or picks a competitor whose facts line up cleanly.<\/p>\n<h2>Which directories do AI engines actually pull from?<\/h2>\n<p><strong>No engine publishes its retrieval list, but citation studies converge on a stable set: review grids (G2, Capterra, Trustpilot, Clutch), entity databases (Wikidata, Crunchbase, LinkedIn), community platforms (Reddit) and encyclopedic sources (Wikipedia).<\/strong> Analyses of large citation datasets \u2014 including Peec AI&#39;s study of roughly 30 million cited sources across ChatGPT, Google AI Mode, Gemini, Perplexity and AI Overviews \u2014 repeatedly put Reddit, YouTube and LinkedIn near the top, with Wikipedia, G2 and Yelp also among the most-cited domains.<\/p>\n<p>Two findings matter more than the ranking itself:<\/p>\n<ul>\n<li><strong>The distribution is long-tailed.<\/strong> Even the single most-cited domain rarely accounts for more than a low-single-digit share of citations; the rest is spread across thousands of domains. There is no one directory to &quot;win&quot; \u2014 presence across several is what builds confidence.<\/li>\n<li><strong>Platforms disagree.<\/strong> Review grids like G2 weigh more heavily in some engines than others, and Wikipedia is cited heavily by some assistants yet lightly by Google&#39;s AI answers. Where your buyers ask changes which directory earns you the citation.<\/li>\n<\/ul>\n<p>The practical read: treat directory presence as a portfolio, not a single bet.<\/p>\n<h2>The three jobs a directory does for an AI answer<\/h2>\n<p><strong>Directories are not interchangeable because AI engines use them for three different jobs: entity resolution, attribute extraction and shortlist generation.<\/strong> Knowing which job a listing serves tells you what to optimize there \u2014 and stops you from pouring effort into a profile that will never move a recommendation.<\/p>\n<ol>\n<li><strong>Entity resolution (who are you?).<\/strong> The model needs to be sure &quot;Acme&quot; the analytics tool is not &quot;Acme&quot; the plumbing franchise. Wikidata, Crunchbase and LinkedIn disambiguate the entity and link its aliases. Get this wrong and every downstream citation is unstable.<\/li>\n<li><strong>Attribute extraction (what&#39;s true about you?).<\/strong> Once resolved, the model pulls facts: category, headquarters, founders, funding, pricing model, integrations. Crunchbase, Wikidata and your Organization schema feed this layer.<\/li>\n<li><strong>Shortlist generation (should I recommend you?).<\/strong> When the query is &quot;best X,&quot; the model leans on category catalogs and review grids \u2014 G2, Capterra, Trustpilot, Clutch \u2014 because they already rank and cluster competitors.<\/li>\n<\/ol>\n<p>Most brands over-invest in job 3 and neglect job 1. <strong>If the entity isn&#39;t resolved, no amount of five-star reviews reliably converts into a recommendation<\/strong>, because the model can&#39;t be confident the reviews describe <em>you<\/em>.<\/p>\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" style=\"max-width:100%;height:auto\" loading=\"lazy\"  src=\"https:\/\/maxaeo.ai\/blog\/wp-content\/uploads\/2026\/07\/1784286455764-13-55777-2.jpg\" alt=\"Framework diagram mapping directories to entity resolution, attribute extraction and shortlist generation for AI answers\"><\/figure>\n<p>Mapping the major directories to those three jobs gives the working stack most B2B brands should build against:<\/p>\n<table>\n<thead>\n<tr>\n<th>Directory<\/th>\n<th>What it is<\/th>\n<th>Primary AEO job<\/th>\n<th>Priority<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Wikidata<\/td>\n<td>Open, machine-readable knowledge graph<\/td>\n<td>Entity resolution<\/td>\n<td>Tier 1<\/td>\n<\/tr>\n<tr>\n<td>Crunchbase<\/td>\n<td>Company, funding and leadership database<\/td>\n<td>Entity + attributes<\/td>\n<td>Tier 1<\/td>\n<\/tr>\n<tr>\n<td>LinkedIn<\/td>\n<td>Verified company profile<\/td>\n<td>Entity confirmation<\/td>\n<td>Tier 1<\/td>\n<\/tr>\n<tr>\n<td>G2, Capterra<\/td>\n<td>B2B software review grids<\/td>\n<td>Shortlist generation<\/td>\n<td>Tier 2<\/td>\n<\/tr>\n<tr>\n<td>Trustpilot<\/td>\n<td>Cross-industry reviews<\/td>\n<td>Trust signal<\/td>\n<td>Tier 2<\/td>\n<\/tr>\n<tr>\n<td>Clutch<\/td>\n<td>Services and agency reviews<\/td>\n<td>Shortlist (services)<\/td>\n<td>Tier 2<\/td>\n<\/tr>\n<tr>\n<td>Vertical \/ niche directories<\/td>\n<td>Industry-specific catalogs<\/td>\n<td>Niche shortlist<\/td>\n<td>Tier 3<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Tier 1: Entity anchors (Wikidata, Crunchbase, LinkedIn)<\/h2>\n<p><strong>Tier 1 sources define your company as a distinct, verifiable entity \u2014 the foundation everything else rests on.<\/strong> Wikidata provides machine-readable properties (founding date, industry, country, founder, official website, external identifiers) that flow directly into the knowledge graphs AI systems consult. Crunchbase adds funding, leadership and category in a structure models parse cleanly. LinkedIn confirms employees, headquarters and activity.<\/p>\n<p>Start here, in this order:<\/p>\n<ul>\n<li><strong>Wikidata.<\/strong> Easier to create than a Wikipedia article and often more directly useful for machines. Add a well-referenced item with the core properties and an official-website statement.<\/li>\n<li><strong>Crunchbase.<\/strong> Claim the profile, write the description in plain language (lead with what you do and who you serve), and keep funding and headcount current.<\/li>\n<li><strong>LinkedIn Company Page.<\/strong> Match the exact legal name, category and one-line description you use everywhere else.<\/li>\n<\/ul>\n<p>Then connect them. Add <code>sameAs<\/code> links in your <a href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/organization\" target=\"_blank\" rel=\"noopener\">Organization schema<\/a> pointing at each Tier 1 profile so engines can stitch the identity together. Schema helps resolution but does not manufacture trust on its own \u2014 we cover those limits in <a href=\"https:\/\/maxaeo.ai\/blog\/organization-schema-ai-search\">what Organization schema can and cannot clarify for AI search<\/a>.<\/p>\n<h2>Tier 2: Category catalogs and review grids (G2, Capterra, Trustpilot, Clutch)<\/h2>\n<p><strong>Tier 2 sources are where shortlist generation happens \u2014 the catalogs that already sort your market into categories and rankings, which is exactly the structure an AI reaches for when a buyer asks &quot;what are the best tools for X.&quot;<\/strong> For B2B software, G2 and Capterra carry outsized weight; for services, Clutch; for cross-industry trust signals, Trustpilot.<\/p>\n<p>Three things move the needle here:<\/p>\n<ul>\n<li><strong>Correct category placement.<\/strong> Being filed under the wrong category is worse than being absent \u2014 you surface when the model shouldn&#39;t recommend you and miss the queries you&#39;d win.<\/li>\n<li><strong>Review volume <em>and<\/em> recency.<\/strong> A cluster of reviews from three years ago reads as a stalled product. Steady, recent reviews signal an active, safe recommendation.<\/li>\n<li><strong>Consistent positioning language.<\/strong> The one-liner buyers and reviewers repeat becomes the phrasing the model echoes. Analyst grids amplify this \u2014 see <a href=\"https:\/\/maxaeo.ai\/blog\/analyst-reports-ai-citations\">how analyst reports and industry grids like the G2 Grid become AI citation fuel<\/a>.<\/li>\n<\/ul>\n<p>Category roundups and &quot;best of&quot; listicles sit adjacent to this tier and are frequently quoted verbatim; our playbook on <a href=\"https:\/\/maxaeo.ai\/blog\/best-of-listicles-ai-search\">getting into the &quot;best [category] tools&quot; roundups AI quotes<\/a> pairs directly with a strong G2 presence.<\/p>\n<h2>Tier 3: Niche and vertical directories<\/h2>\n<p><strong>Tier 3 covers the specialist catalogs for your industry \u2014 vertical marketplaces, association member lists, integration directories and category-specific databases \u2014 which punch above their traffic because they carry topical authority the big platforms lack.<\/strong> A model answering a narrow question (&quot;HIPAA-compliant scheduling tools for clinics&quot;) often surfaces a vertical directory precisely because it&#39;s specific.<\/p>\n<p>These are easy to underestimate. They rarely appear in aggregate &quot;top domains&quot; charts because each one is small \u2014 but in the long tail, where the majority of citations live, they are where niche recommendations are decided.<\/p>\n<p>Prioritize Tier 3 sources that are:<\/p>\n<ul>\n<li><strong>Genuinely used by your buyers<\/strong> (not link farms). If humans don&#39;t cite it, models are less likely to.<\/li>\n<li><strong>Structured<\/strong>, with clear category and description fields rather than a wall of unformatted text.<\/li>\n<li><strong>Editorially maintained<\/strong>, so listings stay accurate and the source keeps its authority.<\/li>\n<\/ul>\n<p>One caution: skip low-quality directory-blasting services. Scattering identical listings across hundreds of scraped catalogs adds noise, not confidence, and can dilute the consistency you&#39;re trying to build.<\/p>\n<h2>How to get accurately listed: a step-by-step order<\/h2>\n<p><strong>The efficient sequence is: lock your canonical facts, anchor the entity, then build category presence \u2014 resolution before reviews.<\/strong> Doing it in this order prevents the common failure where great reviews never convert because the underlying entity is ambiguous.<\/p>\n<ol>\n<li><strong>Write a canonical fact sheet.<\/strong> One source of truth: exact legal name, one-line description, category, HQ, founding year, funding, key people, official URL. Every listing must match this word for word.<\/li>\n<li><strong>Create or complete Wikidata<\/strong>, referencing each fact to a public source.<\/li>\n<li><strong>Claim and complete Crunchbase and LinkedIn<\/strong>, matching the fact sheet exactly.<\/li>\n<li><strong>Add Organization schema<\/strong> with <code>sameAs<\/code> links to all Tier 1 profiles.<\/li>\n<li><strong>Claim G2\/Capterra (or Clutch)<\/strong>, set the correct category, and start a steady review cadence.<\/li>\n<li><strong>Identify 3\u20135 Tier 3 vertical directories<\/strong> your buyers actually use, and list accurately there.<\/li>\n<li><strong>Record every profile URL<\/strong> in a tracking sheet so you can audit and update them later.<\/li>\n<\/ol>\n<p>The whole point of the fact sheet is agreement. <strong>Conflicting descriptions across the web make a model less confident about citing you<\/strong> \u2014 consistency is the single strongest lever in this workflow, and it&#39;s free.<\/p>\n<h2>Why listings decay \u2014 and the maintenance cadence that keeps you cited<\/h2>\n<p><strong>Directory listings decay the moment your company changes and the record doesn&#39;t \u2014 a renamed product, a new funding round, a pivot, an acquisition \u2014 and stale records actively confuse AI answers.<\/strong> This is the gap almost no guide addresses: getting listed is a project; <em>staying accurately listed<\/em> is a discipline.<\/p>\n<p>Common decay patterns:<\/p>\n<ul>\n<li><strong>Old positioning.<\/strong> The listing still describes the product you sold in 2023, so the model recommends you for the wrong use case.<\/li>\n<li><strong>Ghost funding and headcount.<\/strong> Outdated Crunchbase figures make you look smaller or less funded than you are.<\/li>\n<li><strong>Merged or acquired confusion.<\/strong> After an acquisition, two entities blur and the model attributes your capabilities to the wrong company.<\/li>\n<\/ul>\n<p>A workable cadence:<\/p>\n<table>\n<thead>\n<tr>\n<th>Trigger<\/th>\n<th>Update within<\/th>\n<th>Sources to check<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Major launch, rebrand, pivot<\/td>\n<td>1 week<\/td>\n<td>Wikidata, Crunchbase, LinkedIn, G2, website schema<\/td>\n<\/tr>\n<tr>\n<td>Funding, leadership change<\/td>\n<td>2 weeks<\/td>\n<td>Crunchbase, LinkedIn, Wikidata<\/td>\n<\/tr>\n<tr>\n<td>Routine hygiene<\/td>\n<td>Quarterly<\/td>\n<td>All Tier 1\u20133 profiles vs. the canonical fact sheet<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Treat the fact sheet as a living document and reconcile every listing against it on a schedule. Decay is invisible until an AI answer gets you wrong in front of a buyer \u2014 by then you&#39;re reacting, not preventing.<\/p>\n<h2>A worked example: resolving a contradicted entity<\/h2>\n<p><strong>Here is a composite example that mirrors a pattern we see repeatedly: a brand with strong reviews that still wasn&#39;t getting recommended, because its entity was contradicted across sources.<\/strong> The numbers are illustrative; the mechanism is what shows up in tracking data.<\/p>\n<p>A mid-market SaaS company had 200+ positive G2 reviews yet appeared in almost none of the &quot;best tools for [category]&quot; answers tracked across ChatGPT and Perplexity. Three sources disagreed: Crunchbase listed an old product name, Wikidata had no item at all, and the site&#39;s Organization schema used a different legal entity than LinkedIn.<\/p>\n<p>The fix followed the resolution-first order above:<\/p>\n<ol>\n<li>Created a referenced <strong>Wikidata item<\/strong> and linked the official site.<\/li>\n<li>Corrected <strong>Crunchbase<\/strong> to the current name and description.<\/li>\n<li>Aligned <strong>schema <code>sameAs<\/code><\/strong> across the site, LinkedIn and Crunchbase.<\/li>\n<\/ol>\n<p>Over the following weeks, mentions in AI shortlists for the category climbed from near-zero to a regular presence \u2014 <strong>the reviews had always been there; the model finally trusted they described the same company.<\/strong> No new content, no backlinks. Just agreement. Company stage shapes how fast this moves, as we detail in <a href=\"https:\/\/maxaeo.ai\/blog\/ai-visibility-for-startups\">AI search visibility from zero citations to category leader<\/a>.<\/p>\n<h2>How to measure whether directory work moves your AI citations<\/h2>\n<p><strong>Pair directory work with AI search monitoring that tracks how often \u2014 and how accurately \u2014 each engine mentions and recommends you.<\/strong> Directory edits are inputs; your presence in real answers is the output, and the two have to be measured together.<\/p>\n<p>Track three things:<\/p>\n<ul>\n<li><strong>Share of the shortlist.<\/strong> For your target &quot;best X&quot; prompts, what percentage of AI answers include you? This share of voice is the truest scorecard for directory ROI.<\/li>\n<li><strong>Fact accuracy.<\/strong> When engines describe you, do they use your current category, positioning and facts? Drift here points straight back to a stale listing.<\/li>\n<li><strong>Which sources get cited.<\/strong> Knowing <em>which<\/em> directory an engine quoted tells you where to reinforce and where you&#39;re thin.<\/li>\n<\/ul>\n<p>A purpose-built AI visibility monitor closes this loop: it watches how ChatGPT, Gemini, Perplexity, Claude, Copilot and Google&#39;s AI answers mention, rank and describe you, then points to the specific listing to fix next. The goal is a defensible line from &quot;we corrected Crunchbase and Wikidata&quot; to &quot;we now get recommended for our category.&quot; Assistant behavior differs by engine \u2014 <a href=\"https:\/\/maxaeo.ai\/blog\/how-to-get-cited-by-claude\">how Claude searches the web and picks sources<\/a> is a useful model for the assistant many teams use at work.<\/p>\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" style=\"max-width:100%;height:auto\" loading=\"lazy\"  src=\"https:\/\/maxaeo.ai\/blog\/wp-content\/uploads\/2026\/07\/1784286455764-13-55777-3.jpg\" alt=\"AI share of voice dashboard tracking brand mentions in ChatGPT, Gemini and Perplexity from business directories for AI search\"><\/figure>\n<h2>Common mistakes that keep you out of AI answers<\/h2>\n<p><strong>The recurring failures are inconsistency, reviews-before-resolution and set-and-forget listings.<\/strong> Each quietly suppresses citations even when the individual profiles look fine.<\/p>\n<ul>\n<li><strong>Inconsistent facts.<\/strong> Different names, categories or descriptions across profiles \u2014 the number-one confidence killer.<\/li>\n<li><strong>Chasing reviews before the entity is resolved.<\/strong> Volume can&#39;t compensate for an ambiguous identity.<\/li>\n<li><strong>Directory spam.<\/strong> Bulk listings on scraped, low-quality catalogs add noise and erode consistency.<\/li>\n<li><strong>Ignoring platform differences.<\/strong> Optimizing only for one engine when your buyers ask elsewhere.<\/li>\n<li><strong>No maintenance.<\/strong> Treating listings as one-time setup, then letting them decay through your next pivot or raise.<\/li>\n<\/ul>\n<p>Avoiding these five is most of the work. None require budget \u2014 they require discipline and a single source of truth.<\/p>\n<h2>Frequently asked questions<\/h2>\n<p><strong>Do AI search engines really use business directories, or just websites?<\/strong><br \/>\nBoth \u2014 and directories carry extra weight because they&#39;re independent. Citation analyses of tens of millions of AI answers consistently surface directories and review grids (G2, Yelp, Crunchbase-style databases, Wikidata) alongside brand websites. The model trusts an outside record more than your own claim about yourself.<\/p>\n<p><strong>Which business directory should a B2B SaaS company prioritize first?<\/strong><br \/>\nStart with entity anchors \u2014 Wikidata, Crunchbase and LinkedIn \u2014 before review grids. Resolve <em>who you are<\/em> first; then G2 and Capterra reviews reliably convert into shortlist recommendations. Reviews on an unresolved entity often don&#39;t move AI citations.<\/p>\n<p><strong>Does a Crunchbase or Wikidata listing directly get me cited by ChatGPT?<\/strong><br \/>\nNot directly or instantly. These listings feed the knowledge graph and confirm your facts, which raises the model&#39;s confidence to mention you. Citations follow when multiple independent sources agree \u2014 think of it as removing a blocker, not flipping a switch.<\/p>\n<p><strong>How often should I update my directory listings?<\/strong><br \/>\nUpdate Tier 1 sources within one to two weeks of any material change (rebrand, funding, leadership) and run a full quarterly reconciliation against your canonical fact sheet. Stale records are a leading cause of AI answers describing you inaccurately.<\/p>\n<p><strong>Can directory listings hurt my AI visibility?<\/strong><br \/>\nYes \u2014 inconsistent facts across profiles and bulk listings on low-quality catalogs both reduce confidence. Contradiction is worse than absence. Prioritize a handful of authoritative, accurate, consistent listings over broad, noisy coverage.<\/p>\n<hr>\n<p>Getting listed in the databases AI pulls from isn&#39;t a growth hack \u2014 it&#39;s the reference layer your recommendations are built on. Anchor the entity first, earn category presence second, and keep every record honest and current. Then watch the answers to confirm it&#39;s working.<\/p>\n<p><script type=\"application\/ld+json\">\n{\n  \"@context\": \"https:\/\/schema.org\",\n  \"@type\": \"Article\",\n  \"headline\": \"Business Directories for AI Search: Which Ones AI Actually Uses\",\n  \"description\": \"Which business directories and databases ChatGPT, Perplexity and Gemini actually pull from, and how to get accurately listed and kept current \u2014 with a tiering framework and maintenance cadence.\",\n  \"author\": {\n    \"@type\": \"Organization\",\n    \"name\": \"MaxAEO\"\n  },\n  \"publisher\": {\n    \"@type\": \"Organization\",\n    \"name\": \"MaxAEO\",\n    \"logo\": {\n      \"@type\": \"ImageObject\",\n      \"url\": \"https:\/\/maxaeo.ai\/images\/logo.png\"\n    }\n  },\n  \"image\": \"https:\/\/maxaeo.ai\/images\/business-directories-ai-search.png\",\n  \"datePublished\": \"\",\n  \"dateModified\": \"\",\n  \"mainEntityOfPage\": {\n    \"@type\": \"WebPage\",\n    \"@id\": \"https:\/\/maxaeo.ai\/blog\/business-directories-ai-search\"\n  }\n}\n<\/script><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Business directories for AI search: which databases ChatGPT, Perplexity and Gemini pull from, how to get listed accurately, and how to stay cited.<\/p>\n","protected":false},"author":1,"featured_media":1429,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1432","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/posts\/1432","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/comments?post=1432"}],"version-history":[{"count":0,"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/posts\/1432\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/media\/1429"}],"wp:attachment":[{"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/media?parent=1432"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/categories?post=1432"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/tags?post=1432"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}