![\"Get](\"https:\/\/no-cache.hubspot.com\/cta\/default\/53\/9dd5e54b-fbef-4dd0-bc44-1689feb1ea18.png\")
<\/a><\/p>\nAnswer Engine Optimization (AEO) keyword research isn\u2019t just about finding what people search. It\u2019s about understanding what answer engines are asked, how they interpret those prompts, and which questions your content needs to answer directly and authoritatively. The entire mental model shifts from ranking<\/em> to getting cited.<\/em><\/p>\n This guide breaks down exactly how to approach that shift, which tools actually help, and how to build a workflow that connects question discovery to published, AI-optimized content.<\/p>\n Table of Contents<\/strong><\/p>\n <\/a> <\/p>\n Traditional SEO keyword research is grounded in real user data: monthly search volume, keyword difficulty, and potential click-through rate. Tools like Ahrefs<\/a> and Semrush surface what people type into Google, and you optimize content to rank for those terms.<\/p>\n AEO flips several of those assumptions.<\/p>\n SEO keyword research prioritizes:<\/strong><\/p>\n AEO keyword research prioritizes:<\/strong><\/p>\n The practical difference is that when someone asks ChatGPT, \u201cWhat\u2019s the best CRM for a small marketing team?\u201d, the model doesn\u2019t return a ranked list of pages. Instead, it synthesizes an answer from content it has indexed and deemed authoritative.<\/p>\n Your job is to be the source the model trusts.<\/p>\n AEO keyword research tools help discover conversational and question-based queries that align with how users prompt answer engines. AEO tools differ from SEO tools in that they focus on answer engine visibility, prompt patterns, and answer-first content opportunities \u2014 not just search volume and backlinks.<\/p>\n Pro <\/strong>t<\/strong>ip:<\/strong> Start your AEO keyword research by reading your own brand\u2019s AI Overview appearances in Google. Search for your category (e.g., \u201cbest email marketing software\u201d) and note which questions trigger AI-generated summaries.<\/p>\n Those are the AEO targets worth owning first.<\/p>\n <\/a> <\/p>\n There\u2019s no single \u201cAEO keyword tool.\u201d The best stack combines traditional question-discovery tools with newer answer engine visibility trackers and synthetic query generators. Here\u2019s how I categorize them, and which ones I\u2019d actually use.<\/p>\n Traditional SEO tools are still essential for AEO, but you need to know how to use them differently. Rather than chasing high-volume head terms, I use these tools to isolate question-based queries, extract \u201cPeople Also Ask\u201d clusters, and identify long-tail prompts that map to conversational search behavior.<\/p>\n AEO keyword research builds on this foundation: these tools give you a baseline understanding of what people ask, which you can then expand through fanout analysis and AI prompt modeling.<\/p>\n Semrush\u2019s Keyword Magic Tool lets you filter by question-type queries (who, what, how, why, when), which is exactly the format AEO content needs to answer. I\u2019ve found the \u201cQuestions\u201d filter in Semrush particularly useful for identifying how a topic branches into multiple user intents \u2014 a precursor to fanout query mapping.<\/p>\n What we like:<\/strong> The Topic Research feature surfaces semantically related questions and subtopics in a visual card format, making it easy to spot content gaps around a core AEO theme.<\/p>\n Pro <\/strong>t<\/strong>ip:<\/strong> Export Semrush\u2019s \u201cQuestions\u201d results for your top 5\u201310 seed keywords. This is your starting question inventory. From there, you can use fanout tools (covered below) to expand it into an AI-native set of prompts.<\/p>\n Best for:<\/strong> Enterprise teams that need breadth across question discovery, competitive gap analysis, and content optimization in one platform.<\/p>\n Ahrefs\u2019 Content Explorer and Site Explorer let you see which pages on competitor sites earn the most links and traffic \u2014 useful for identifying which AEO-style content (FAQs, guides, comparison pages) signals authority.<\/p>\n The \u201cQuestions\u201d filter in Keywords Explorer is another solid source of conversational queries.<\/p>\n What we like:<\/strong> Ahrefs\u2019 \u201cAlso rank for\u201d report shows what else a page ranks for \u2014 great for uncovering the semantic neighborhood around your target AEO topics. See our roundup of the best tools to find long-tail keywords<\/a> for more options in this category.<\/p>\n Best for:<\/strong> Teams that want deep keyword data, strong competitor content analysis, and reliable search volume estimates.<\/p>\n AlsoAsked scrapes Google\u2019s \u201cPeople Also Asked\u201d data and presents it as a visual tree \u2014 showing how one question branches into related sub-questions. This is one of the most direct inputs for AEO content structure: the branches represent the natural follow-up prompts users ask after an initial query, which is close to how LLM fanout works.<\/p>\n What we like:<\/strong> The visual hierarchy makes it immediately obvious which questions are \u201cparent\u201d questions (likely your H2s) and which are sub-questions (your H3s and direct answers). It\u2019s one of the tools I use almost every time I\u2019m building an AEO content brief.<\/p>\n Best for:<\/strong> Mapping question hierarchies and understanding how people move from broad questions to specific follow-ups.<\/p>\n AnswerThePublic visualizes question-based and preposition-based queries around a seed keyword. It\u2019s a fast way to generate a large pool of AEO candidates, organized by question type (what, how, why, can, will, etc.).<\/p>\n What we like:<\/strong> The export function makes it easy to pipe hundreds of question variants into a spreadsheet for prioritization. Pair it with Semrush or Ahrefs volume data to identify which questions actually have search demand.<\/p>\n Best for:<\/strong> Broad question discovery across a topic, especially for teams new to AEO who need to see the full landscape of what people ask.<\/p>\n LLM query fan-outs reveal related prompts, comparisons, and follow-up questions triggered by a single input. When someone types \u201chow do I choose a CRM\u201d into ChatGPT, the model may internally generate and answer multiple sub-queries before surfacing a response.<\/p>\n Understanding that fanout is one of the most underutilized levers in AEO keyword research.<\/p>\n Question discovery tools surface people-first questions and long-tail prompts \u2014 fanout tools take that a step further by modeling how AI systems expand and interpret those questions.<\/p>\n Otterly.ai monitors visibility across ChatGPT, Perplexity, and other answer engines. By tracking which prompts trigger your content\u2019s inclusion, you can reverse-engineer the fanout clusters that matter most.<\/p>\n What we like:<\/strong> Otterly surfaces prompt visibility by platform \u2014 so you can see that you\u2019re appearing in Perplexity for \u201cbest CRM for small teams\u201d but not in ChatGPT for the same query. That gap analysis is directly actionable.<\/p>\n Best for:<\/strong> Teams that want to see how their brand and content show up across multiple AI platforms, and use that data to guide prompt targeting.<\/p>\n Dejan.ai offers tools for semantic analysis, entity mapping, and understanding how AI systems interpret content. Entity mapping improves content clarity and citation likelihood \u2014 and Dejan\u2019s tools help you model those relationships before writing.<\/p>\n What we like:<\/strong> The entity-level analysis is more sophisticated than most tools in this category. If you\u2019re serious about structured AEO content that AI systems can parse and cite confidently, Dejan.ai is worth exploring.<\/p>\n Best for:<\/strong> Advanced SEO and AEO practitioners who want to model semantic query expansion and understand how entities relate to each other in AI-generated answers.<\/p>\n This pairing is one of my favorite DIY approaches to fanout query modeling. Use Screaming Frog to crawl your site and extract existing H2s, H3s, and meta descriptions.<\/p>\n Feed those into Gemini via the API (or Google AI Studio) with a prompt like: \u201cWhat follow-up questions would users ask after reading about [topic]? List 10 specific, conversational questions.\u201d<\/em> The output gives you a synthetic fanout \u2014 an approximation of how AI models expand your current content\u2019s topical footprint.<\/p>\n Pro <\/strong>t<\/strong>ip:<\/strong> Run this process on your top-performing pages first. If a page already earns traffic or visibility for a topic, expanding its AEO coverage through fanout question integration is lower-effort than building from scratch.<\/p>\n Best for:<\/strong> Technical SEO teams who want to use existing crawl infrastructure to enrich content with AI-generated question expansion.<\/p>\n AEO trackers measure mentions, citations, and visibility across answer engines \u2014 filling the gap that traditional rank trackers leave completely empty. Competitive insights from these tools help you determine gaps in coverage \u2014 where competitors appear and which prompts brands are missing entirely.<\/p>\n The HubSpot AEO Grader supports a baseline answer engine visibility assessment \u2014 and it\u2019s the tool I\u2019d recommend to any team just starting to measure their AEO performance. It shows you how your brand appears across AI-powered search results, where you have authority, and where your content falls short.<\/p>\n What we like:<\/strong> It\u2019s free and delivers immediate clarity on answer engine visibility. Use it to gain leadership buy-in before committing to a broader investment in an AEO tool.<\/p>\n Best for:<\/strong> Teams that want a free, fast baseline assessment of their answer engine visibility before investing in a full AEO tool stack.<\/p>\n HubSpot\u2019s AEO product includes prompt tracking that lets you monitor which questions your brand appears for across answer engines \u2014 and AI-powered suggestions that actively recommend new prompts and questions to track based on your existing visibility and content gaps.<\/p>\n This is the feature I find most valuable: the tool doesn\u2019t just show you where you are \u2014 it tells you where to go next. It surfaces additional questions to monitor based on semantic similarity and competitor coverage, which effectively automates a significant portion of the fanout discovery process.<\/p>\n What we like:<\/strong> HubSpot AEO produces a single answer engine visibility score across ChatGPT, Perplexity, and Gemini, then translates the underlying data into plain-language recommendations any marketing team can act on without an AEO specialist on staff. The competitor comparison view makes citation gaps immediately obvious.<\/p>\n Best for: <\/strong>Marketing teams that want a fast baseline of their answer engine visibility plus a prioritized roadmap for closing the gaps, without stitching together multiple monitoring tools.<\/p>\n AEO is built into Marketing Hub Pro and Enterprise<\/a>, which means the same visibility score, prompt tracking, and recommendations connect directly to the CRM, content, and reporting tools marketing teams already use. Because it draws from CRM data, prompt suggestions auto-tune to specific industries, competitors, and customer segments \u2014 and recommendations get sharper the longer the platform learns the business.<\/p>\n What we like:<\/strong> Teams can see their AEO gaps and seamlessly create content in Content Hub. Native integration means the different tools work together.<\/p>\n Pro tip:<\/strong> Set up prompt tracking for your top 10 to 15 primary AEO targets first. After 30 days, use the AI-powered suggestions to expand to the next tier of prompts.<\/p>\n Best for:<\/strong> Marketing teams that want their AEO research, tracking, and execution unified inside the platform already running their content and pipeline reporting. This staged approach keeps your tracking focused and actionable rather than overwhelming your team with hundreds of data points at once.<\/p>\n Synthetic query generation lets you approximate the range of prompts users might type into answer engines \u2014 without waiting for organic search data to accumulate. This is especially valuable for newer products, emerging categories, or topics that don\u2019t yet have established search volume.<\/p>\n Claude is one of my go-to tools for generating synthetic queries.<\/p>\n A prompt like: \u201cYou are an expert in [topic]. Generate 20 distinct questions a user might ask an AI assistant about [topic], ranging from beginner to advanced, including comparison questions and follow-ups\u201d<\/em> produces a high-quality starting inventory.<\/p>\n The higoodie.com query fan-out methodology<\/a> outlines a structured approach: start with query analysis to understand intent, then expand to related prompts, and finally map to content gaps. Claude handles all three stages well.<\/p>\n What we like:<\/strong> Claude is particularly good at generating comparative and consideration-stage queries \u2014 \u201cClaude vs. ChatGPT for customer support,\u201d \u201cwhich CRM integrates best with HubSpot\u201d \u2014 that reflect how real users prompt answer engines when making purchasing decisions.<\/p>\n Pro <\/strong>t<\/strong>ip:<\/strong> After generating synthetic queries, test them directly in ChatGPT and Perplexity. Note which ones return AI-generated answers (versus a traditional results page) \u2014 those are your highest-priority AEO targets.<\/p>\n Best for:<\/strong> Generating rich synthetic prompt sets, modeling fanout queries, and validating whether your content directly answers the questions that answer engines are likely to field.<\/p>\n See our guide on AI SEO<\/a> for more context on optimizing for AI-generated answers.<\/p>\n <\/a> <\/p>\n The tools above are only as useful as the workflow connecting them. Here\u2019s the process I\u2019d recommend for a team starting AEO keyword research from scratch \u2014 or auditing an existing program.<\/p>\n Start with five to 10 core topics your brand owns or wants to own. These are typically product categories, use cases, or customer problems \u2014 not branded terms.<\/p>\n Type each seed topic into Google and capture autocomplete suggestions. These are real, high-frequency queries that often match answer engine prompt patterns. Focus especially on question-format autocomplete (\u201chow do I,\u201d \u201cwhat is the best,\u201d \u201cwhy does\u201d).<\/p>\n For each seed topic, search Google and take a screenshot of the \u201cPeople Also Asked\u201d box. Use AlsoAsked to expand this into a full question hierarchy. This gives you a two-level map: primary questions (what people ask first) and follow-up questions (what they ask next). Both matter for AEO.<\/p>\n Cross-reference your PAA question list with Semrush or Ahrefs to identify which questions have meaningful search volume. High-volume questions with AI Overview appearances in the SERP are your top AEO targets \u2014 they already have AI-generated answers, which means appearing in them is achievable with the right content.<\/p>\n Take your prioritized list of questions and group them by intent cluster. \u201cWhat is X,\u201d \u201cHow does X work,\u201d and \u201cX vs. Y\u201d are different intent clusters that require different content treatments.<\/p>\n Feed each cluster into Claude or ChatGPT with a fanout prompt: \u201cA user asks: \u2018[primary question]\u2018. What are 8 follow-up questions they might ask after receiving an answer?\u201d<\/em> Document the output.<\/p>\n Test your top synthetic prompts in ChatGPT, Perplexity, and Gemini. Record which prompts generate AI-synthesized answers and which return standard links. AI-generated answer triggers are your AEO keywords.<\/p>\n For each confirmed AEO target, check whether your site currently appears in the AI-generated answer. Use HubSpot\u2019s AEO prompt tracking or Otterly.ai to systematize this. Gaps become your content roadmap.<\/p>\n For each confirmed gap, create a content brief that includes:<\/p>\n Content briefs for AEO should include the core question, direct answer, supporting entities, schema, and internal links. This is where the research workflow connects to execution \u2014 and where most teams drop the ball by keeping their AEO insights in a spreadsheet that never reaches the writer.<\/p>\n <\/a> <\/p>\n No, but AEO is expanding the scope of what SEO teams are responsible for. Traditional organic search isn\u2019t disappearing \u2014 Google still serves billions of queries that return traditional results pages \u2014 but the share of queries resolved by AI-generated answers is growing, and that trend is accelerating.<\/p>\n Teams that treat AEO as a complement to SEO, not a replacement, are better positioned than those waiting to see which wins. The underlying skills overlap significantly \u2014 technical soundness, strong content, and authority signals matter in both worlds \u2014 but targeting, structure, and measurement diverge. For a deeper look at this shift, see our guide on answer engine optimization<\/a>.<\/p>\n ChatGPT is a useful tool for synthetic query generation and fanout expansion, but it\u2019s not sufficient on its own. It doesn\u2019t provide search volume data, can\u2019t track your answer engine visibility over time, and doesn\u2019t show you where competitors appear.<\/p>\n Use it as a question-generation and validation layer on top of tools that provide real search data (Semrush, Ahrefs) and answer engine visibility tracking (HubSpot AEO, Otterly.ai). ChatGPT is a strong input to the research process; it\u2019s not the research platform.<\/p>\n Start with Google AI Overviews. Google still holds the largest share of global search traffic, and AI Overviews are appearing for an expanding range of commercial and informational queries. Appearing in a Google AI Overview often requires meeting the same E-E-A-T standards that traditional Google ranking does \u2014 so existing SEO investment carries over more directly. See our guide on Google E-E-A-T<\/a> for what\u2019s required to earn that trust.<\/p>\n Once the team has a baseline Google AEO program, expand to Perplexity (strong with researchers and technically sophisticated users) and ChatGPT (relevant for purchase consideration and comparison queries). Multi-engine coverage is a reasonable goal within 6 to 12 months \u2014 but it\u2019s not where most teams should start.<\/p>\n More frequently than traditional SEO research. Answer engines regularly update their indexing and answer generation, and new fanout patterns emerge as user behavior evolves. My recommendation: run a full AEO keyword audit quarterly and review prompt-tracking data monthly.<\/p>\n If you\u2019re using a tool like HubSpot\u2019s AEO product with AI-powered suggestions, let the tool flag emerging prompt opportunities between formal review cycles. The worst outcome in AEO is building content for questions that answer engines have stopped answering \u2014 so staying current with your prompt coverage is an ongoing operational requirement, not a one-time project.<\/p>\n It depends on team size and maturity. An exploratory stack under $500 per month can combine free tools like the HubSpot AEO Grader, Google Search Console, and AnswerThePublic\u2019s free tier with AlsoAsked ($15\u201349 per month) and Claude Pro ($20 per month) \u2014 enough to cover question discovery, fanout generation, and basic visibility checking.<\/p>\n A growth-stage stack of $500\u2013$2,000 per month typically adds Semrush or Ahrefs ($120\u2013$500 per month, depending on tier), Otterly.ai for answer engine tracking, and HubSpot AEO for integrated prompt tracking and suggestions. The biggest mistake teams make is investing in a six-figure stack before the workflow to act on the data is built \u2014 start with the minimum viable tool set, prove the process works, then scale up. See our roundup of the best rank trackers<\/a> for more on AI-integrated rank monitoring.<\/p>\n <\/a> <\/p>\n AEO keyword research isn\u2019t one job \u2014 it\u2019s three. Discovering the questions buyers ask, modeling how AI answer engines expand those questions into fanout prompts, and tracking which prompts the brand actually appears for. No single tool covers all three categories well, which is why the right stack matters more than any single platform.<\/p>\n For teams that want a unified starting point, HubSpot AEO consolidates the visibility, tracking, and recommendation layers in one place. It produces a single answer engine score across ChatGPT, Perplexity, and Gemini, shows which prompts cite competitors instead of the brand, and delivers prioritized, plain-language recommendations starting at $50 per month. Marketing Hub Pro and Enterprise extend that with CRM-powered prompt suggestions that help teams address gaps.<\/p>\n The fastest way to see where the brand stands today is the free HubSpot AEO Gra<\/a>der<\/a>. It\u2019s a baseline check, not a commitment \u2014 and it\u2019s the cleanest first step into a structured AEO program.<\/p>\n When I first started auditing content for answer engine visibility, I assumed the keyword research process was roughly<\/p>\n","protected":false},"author":1,"featured_media":3237,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[14],"tags":[],"_links":{"self":[{"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/posts\/3235"}],"collection":[{"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/comments?post=3235"}],"version-history":[{"count":2,"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/posts\/3235\/revisions"}],"predecessor-version":[{"id":3247,"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/posts\/3235\/revisions\/3247"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/media\/3237"}],"wp:attachment":[{"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/media?parent=3235"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/categories?post=3235"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/tags?post=3235"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
How Keyword Research Differs for AEO vs. SEO<\/h2>\n
\n
\n
Keyword Research Tools for AEO by Goal<\/h2>\n
Traditional Keyword Research Tools<\/h3>\n
Semrush<\/a><\/h4>\n
![\"key](\"http:\/\/fliegewiese.org\/wp-content\/uploads\/2026\/04\/key20word20research20tools20for20aeo2c20semrush.jpg\")
<\/p>\nAhrefs<\/a><\/h4>\n
AlsoAsked<\/a><\/h4>\n
![\"key](\"http:\/\/fliegewiese.org\/wp-content\/uploads\/2026\/04\/key20word20research20tools20for20aeo2c20also20asked.png\")
<\/p>\nAnswerThePublic<\/a><\/h4>\n
![\"key](\"http:\/\/fliegewiese.org\/wp-content\/uploads\/2026\/04\/key20word20research20tools20for20aeo2c20answer20the20public.png\")
<\/p>\nTools for Finding Fanout Queries<\/h3>\n
Otterly.ai<\/a><\/h4>\n
![\"key](\"http:\/\/fliegewiese.org\/wp-content\/uploads\/2026\/04\/key20word20research20tools20for20aeo2c20otterly.png\")
<\/p>\nDejan.ai<\/a><\/h4>\n
![\"key](\"http:\/\/fliegewiese.org\/wp-content\/uploads\/2026\/04\/key20word20research20tools20for20aeo2c20dejan.png\")
<\/p>\nScreaming Frog<\/a> + Gemini<\/a><\/h4>\n
AEO Visibility Trackers<\/h3>\n
HubSpot AEO Grader<\/a><\/h4>\n
![\"key](\"http:\/\/fliegewiese.org\/wp-content\/uploads\/2026\/04\/key20word20research20tools20for20aeo2c20aeo20grader.jpg\")
<\/p>\nHubSpot AEO<\/a> \u2014 Prompt Tracking & AI-Powered Suggestions<\/em><\/h4>\n
![\"key](\"http:\/\/fliegewiese.org\/wp-content\/uploads\/2026\/04\/key20word20research20tools20for20aeo2c20hubspot20aeo.png\")
<\/p>\nMarketing Hub Pro and Enterprise<\/em><\/h4>\n
![\"key](\"http:\/\/fliegewiese.org\/wp-content\/uploads\/2026\/04\/key20word20research20tools20for20aeo2c20hubspot.png\")
<\/p>\nTools for Ideating AI Prompts With Synthetic Query Generation<\/h3>\n
Claude<\/a><\/h4>\n
![\"key](\"http:\/\/fliegewiese.org\/wp-content\/uploads\/2026\/04\/key20word20research20tools20for20aeo2c20claude.jpg\")
<\/p>\nStep-by-Step Workflow to Find AEO Keywords<\/h2>\n
How to Use Autocomplete and People Also Ask for AEO<\/h3>\n
Step 1: Seed query identification.<\/strong><\/h4>\n
Step 2: Autocomplete expansion.<\/strong><\/h4>\n
Step 3: People Also Asked mapping.<\/strong><\/h4>\n
Step 4: Prioritization.<\/strong><\/h4>\n
How to Use LLM Query Fan-Outs to Expand Question Sets<\/h3>\n
Step 1: Query analysis.<\/strong><\/h4>\n
Step 2: Synthetic expansion.<\/strong><\/h4>\n
Step 3: Cross-engine validation.<\/strong><\/h4>\n
Step 4: Gap analysis.<\/strong><\/h4>\n
Step 5: Content brief creation.<\/strong><\/h4>\n
\n
Frequently Asked Questions About Keyword Research Tools for AEO<\/h2>\n
Is AEO replacing SEO?<\/h3>\n
Can I use ChatGPT alone for AEO keyword research?<\/h3>\n
Which engine should I prioritize first for AEO?<\/h3>\n
How often should I refresh AEO keyword research?<\/h3>\n
What budget should I plan for AEO tools?<\/h3>\n
How to Choose Your AEO Keyword Research Stack<\/h2>\n
![\"\"](\"https:\/\/track.hubspot.com\/__ptq.gif?a=53&k=14&r=https%3A%2F%2Fblog.hubspot.com%2Fmarketing%2Fkeyword-research-tools-for-aeo&bu=https%253A%252F%252Fblog.hubspot.com%252Fmarketing&bvt=rss\")
<\/p>\n","protected":false},"excerpt":{"rendered":"