Installing AIOSEO is the easy part. Running the setup wizard, selecting your site type, connecting Search Console, generating your sitemap. Five minutes and it feels like your SEO is sorted.
It is not sorted. Not yet.
The setup wizard gets you to a workable baseline. It does not get you to an optimised configuration. There are seven specific settings that the wizard either skips entirely, sets to a default that works for most sites but not yours, or buries in a submenu that most bloggers never find. These are not obscure edge cases. They are the settings that determine whether your site is properly readable to Google, to ChatGPT, to Perplexity, and to every other platform that is increasingly deciding which content is worth surfacing to its users.
The Marketing Shelf spent the first few weeks after launch discovering each of these gaps one by one. Some of them cost indexed posts. One of them meant a month of publishing without proper entity verification for AI search. None of them were obvious from the wizard alone.
If you are already using AIOSEO, go through this list and check each setting right now. If you are not using AIOSEO yet and you want a plugin that handles WordPress SEO reliably without requiring you to think about it constantly, you can get started below.
Why Most AIOSEO Configurations Are Incomplete
The setup wizard does a good job of covering the visible, obvious settings. Site name, tagline, sitemap, social profiles. These are the things that are easy to explain in a five-step wizard and that most bloggers know they should configure.
What the wizard cannot do is make the judgment calls that depend on your specific site, your publishing strategy, and what you want your content to rank for. It cannot tell you which pages should be noindexed because they are not worth Google’s crawl budget.
It cannot set up the entity signals that AI search systems use to verify your brand exists independently of your website. It cannot add the structured data fields that improve your citation probability across every major AI platform.
These are the decisions a wizard can present to you, but only you can make them correctly, and most bloggers do not know they need to make them at all.
The good news is that fixing all seven of the settings below takes less than an hour in total and most of them take under five minutes each. The impact they have on your site’s visibility, in both traditional Google search and AI search, is meaningful and lasting.
Organization Schema Is Incomplete or Missing
This is the single most impactful oversight in most AIOSEO configurations and the one with the most direct effect on AI search visibility. Most bloggers fill in their site name and logo during the wizard and assume Organization schema is done. It is not.
The part that matters most for AI citation is the same as property, which links your brand to verified external profiles. This is how AI systems confirm that your website belongs to a real, identifiable entity rather than an anonymous collection of web pages. ChatGPT, Perplexity, and Google AI Overviews all evaluate entity signals when deciding whether to cite a source. A brand with verified same as links to LinkedIn, Twitter, and other profiles is more citable than one without them.
To fix this, go to All in One SEO in your WordPress dashboard, then click on Search Appearance, then scroll down to Knowledge Graph. Make sure your site name is set correctly, your logo is uploaded, and then look for the Social Networks section. Add every social profile URL you have, LinkedIn, Twitter or X, Instagram, Pinterest, YouTube. Each one becomes a sameAs link in your Organization schema.
While you are in the Knowledge Graph settings, also check whether your site is set up as a Person or an Organization. Solo bloggers often accidentally set this to Organization when Person is more accurate, or vice versa. A personal brand should typically be configured as Person with your full name and a link to your professional bio. A publication or business should be configured as Organization. This distinction affects how your entity is represented in Google’s Knowledge Graph and how AI systems categorise your brand.
Author Schema Has No Credentials
Author schema is one of the clearest E-E-A-T signals available in your WordPress configuration, and almost every blogger leaves it half-finished.
AIOSEO pulls author information from your WordPress user profile when generating Article schema for your posts. If your user profile has no biographical information, no external profile links, and no description of your expertise, your author schema is generated but it says almost nothing meaningful about who wrote the content. An Article schema that lists an author with a name and nothing else provides no E-E-A-T signal. It is the structured data equivalent of a byline on a business card with no job title.
The fix is in your WordPress user profile, not in AIOSEO settings. Go to Users, then Your Profile, and complete the Biographical Info field with a genuine description of your relevant expertise and experience. Then go to the AIOSEO profile fields that appear below the standard WordPress profile fields and add your LinkedIn URL, your Twitter profile, and any other professional profile that demonstrates your credentials in your niche.
Every post you publish after completing this will have Author schema that includes your credentials and links to verifiable professional profiles. For a post on AI marketing, that means the author schema confirms the person who wrote this covers AI marketing professionally and has a LinkedIn profile where that claim can be verified. That is the trust signal that AI systems are looking for when evaluating whether to cite a source.
The Wrong Pages Are Being Indexed
Most bloggers leave every page on their WordPress site set to index by default. This is one of the most common technical SEO mistakes and it is costly in a way that is not immediately obvious.
Google has a crawl budget. It allocates a certain amount of crawling resources to your site based on its authority and size. If you are sending Google to index your tag pages, your date archive pages, your author archive page, your search results page, and every pagination variation of your category pages, you are consuming crawl budget on pages that provide no SEO value and potentially diluting your site’s topical authority by creating dozens of thin or duplicate pages in Google’s index.
The pages that should almost always be set to noindex are tag archives, date archives, author archives if you are the only author on the site, search results pages, and pagination pages beyond page one of any archive. These pages either duplicate content that exists elsewhere on your site, contain no original content worth indexing, or create canonicalization issues that confuse rather than help your rankings.
In AIOSEO, go to Search Appearance, then click on Content Types, then Taxonomies. Look for Tags. For most blogs, tags serve an organisational purpose for the reader but their archive pages are low-value for search. Set tag archives to noindex. Then go to Archives and set Date Archives and Author Archives to noindex unless you have a specific reason to index them.
While you are in Search Appearance, also check the Crawl Cleanup settings if you are on a paid plan. This feature lets you disable feeds, emoji scripts, and other WordPress defaults that add unnecessary URLs to your site’s footprint. Reducing the number of low-value URLs your site generates keeps your crawl budget focused on the content that actually matters.
IndexNow Is Not Enabled
IndexNow is one of the most underused settings in AIOSEO and one of the most valuable for getting new content discovered quickly.
IndexNow is an open protocol that allows you to notify search engines immediately when you publish or update content, rather than waiting for them to recrawl your site on their own schedule. When you publish a new post, AIOSEO can ping Bing and other connected search engines via IndexNow within seconds of publishing. Bing then indexes the content quickly, making it available for ChatGPT Search and Siri, both of which use Bing’s index as their primary source for live web retrieval.
Most bloggers never enable this setting because it is not part of the setup wizard and it sits in a submenu that requires knowing to look for it.
To enable it, go to All in One SEO, then click on Sitemap, and look for the IndexNow tab. Enable it and verify that your API key is generated and active. AIOSEO handles the key generation automatically once you enable the feature. From that point forward, every post you publish or significantly update is pinged to Bing automatically without any additional action on your part.
The compounding benefit of IndexNow is speed of AI search eligibility. A post that is indexed by Bing on the day of publication is eligible for ChatGPT Search citations that same week. A post that waits two weeks for Bing’s next organic crawl of your site misses that window. For a content site publishing regularly, this difference accumulates into a meaningful advantage in AI search visibility over time.
AI Crawler Access Is Not Verified
Publishing high-quality content means nothing to ChatGPT or Perplexity if their crawlers are blocked from reading it. This setting is outside AIOSEO’s control directly, but AIOSEO gives you access to your robots.txt file where this is configured.
The default WordPress robots.txt file does not block AI crawlers, but many WordPress security plugins, performance plugins, and hosting providers add robots.txt rules that unintentionally block AI crawlers alongside other bots. If you have installed a security plugin, a CDN service, or changed your robots.txt manually at any point, there is a meaningful chance that GPTBot, PerplexityBot, ClaudeBot, or Google-Extended is blocked without you knowing.
To check and fix this, go to All in One SEO, then Tools, then Robots.txt Editor. This shows you your current robots.txt configuration. Look for any Disallow rules that apply to the crawlers listed above. The correct configuration for each AI crawler is a specific Allow rule at the top of the robots.txt file.
The rules you want to confirm are present or add if they are missing are:
Allow: /
User-agent: Google-Extended
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: meta-externalagent
Allow: /
If any of these are not present, add them. If you see a Disallow: / rule applying to any of these crawlers, remove it. This one change has more impact on AI search visibility than any amount of schema markup or content optimisation because schema and content are irrelevant if the crawler cannot read the page to begin with.
FAQPage Schema Is Not Being Added to Posts
FAQPage schema is one of the highest-impact structured data implementations for AI search visibility in 2026 and most AIOSEO users never set it up on a per-post basis because the schema panel in the editor is easy to overlook.
Google removed FAQ rich results from the traditional search results page in May 2026, which led some bloggers to conclude that FAQPage schema was no longer worth implementing. This is wrong in an important way. FAQPage schema lost its visual rich result in Google’s traditional SERP, but it retained its full value for Perplexity, Bing Copilot, ChatGPT, and Google AI Overviews. These platforms specifically look for structured question and answer pairs when deciding how to synthesise responses to informational queries. A post with FAQPage schema provides those pairs in a machine-readable format that dramatically improves extraction probability compared to FAQ content embedded in prose alone.
To add FAQPage schema to a post in AIOSEO, scroll down to the AIOSEO meta box below the post editor, click the Schema tab, and then click Add Schema Graph. Select FAQ from the schema type options. A form appears asking for question and answer pairs. Enter five to ten questions and answers that match what real users would ask about the topic of your post. Each answer should be complete in 40 to 80 words and should be self-contained, meaning it makes full sense without requiring the reader to have read the rest of the post.
The questions you write in this schema should mirror the exact phrasing of People Also Ask results for your target keyword. This is not a coincidence. Google’s People Also Ask data reflects the actual questions users are typing and speaking. When your FAQPage schema answers those exact questions, your extraction probability for AI responses to those queries increases meaningfully.
The entire process takes two minutes per post once you have done it two or three times and have the rhythm of it. Over a publishing year, the difference in AI citation frequency between posts that have FAQPage schema and posts that do not is consistent enough to make it a non-negotiable step in the publishing checklist.
The Title Format Is Using WordPress Defaults
The title format setting controls how AIOSEO generates the meta title for pages, archives, and posts that do not have a manually set title. Most bloggers leave this on the default WordPress setting, which appends the site name to every title in a format like Post Title — Site Name. This is fine but it is not optimised, and for a new site where title space is precious, the default format often wastes characters that could be spent on keywords.
Go to All in One SEO, then Search Appearance, then Global Settings. Look at the Title Format field. The default format uses the post title plus a separator plus the site name. For most blog posts, the site name at the end of the title is consuming around 15 to 25 characters that Google truncates anyway once the title exceeds 60 characters.
For a post with a long title, adding the site name at the end guarantees that Google will truncate the title in the search result, cutting off part of your actual post title to make room for the site name. The reader sees a truncated version of your title that may not communicate the post’s value clearly.
The fix is to set your title format to post title only for individual posts, and then use the Title Separator and site name only for your homepage, where the brand name in the title is genuinely valuable for recognition. AIOSEO allows you to set different title formats for different content types, so posts can use one format while the homepage uses another.
Also check the separator character while you are in this setting. The default separator in most WordPress configurations is a vertical bar or a dash. AIOSEO lets you change this to an em dash substitute, a bullet, or a simple pipe. The visual choice is minor but it contributes to the overall professionalism of how your results appear in the SERP.
While you are in Global Settings, review the Meta Description format as well. AIOSEO can auto-generate meta descriptions from the post excerpt if you have not written one manually. The auto-generated descriptions are rarely as good as a manually written one, but for posts where you have not set a description, having a reasonable auto-generated fallback is better than nothing.
Bonus — Three More Quick Wins Worth Checking
The seven settings above are the main ones that have meaningful ongoing impact. These three are quicker to fix and worth doing while you are already in the settings.
1. XML Sitemap Priority Settings
Your XML sitemap priority settings are almost certainly wrong. AIOSEO assigns priority values to your pages in the sitemap ranging from 0.1 to 1.0. The default assigns high priority to everything, which defeats the purpose of priority signals entirely. Set your homepage to 1.0, your most important pillar pages to 0.8, your regular posts to 0.5 or 0.6, and your less important pages like your privacy policy to 0.1. This gives Google meaningful guidance about which content deserves the most crawl attention.
2. Canonical URL Verification
Your canonical URL settings should be verified to ensure AIOSEO is generating correct canonical tags for all content types. Pagination is the most common source of canonical errors. Make sure your paginated pages are correctly canonicalised to the root page rather than treating each pagination as a separate canonical URL.
3. Bing Webmaster Tools Integration
Your Webmaster Tools verification should include Bing Webmaster Tools, not just Google Search Console. AIOSEO has a dedicated field for Bing verification in the Webmaster Tools section. Adding your Bing Webmaster Tools verification code takes two minutes and it unlocks Bing’s own analytics for your site, which shows you how your content performs in Bing’s index, the same index that feeds ChatGPT Search and Siri.
Subscribe to The Marketing Shelf
If you want practical guides like this one every week, on what actually moves the needle in SEO, AI search, and content strategy in 2026, without the fluff and the five-star affiliate reviews, subscribe to The Marketing Shelf newsletter below. One email a week. Direct, useful, honest.
Welcome to The Marketing Shelf! You’re officially on the list.
No spam. Unsubscribe at any time.
CONCLUSION:
Most bloggers install AIOSEO, finish the wizard, and publish their first post feeling like the SEO is handled. It is partially handled. The seven settings above are what gets it from partially to properly.
To recap quickly. Make sure your Organization schema has sameAs links to your external profiles. Complete your author profile with credentials and professional links. Set tag archives, date archives, and author archives to noindex.
Enable IndexNow in the Sitemap settings. Verify your robots.txt allows all major AI crawlers. Add FAQPage schema to every post through the Schema panel. And fix your title format so you are not wasting character space on site names in post titles that are already long enough.
None of these take more than ten minutes each. The cumulative effect on your technical SEO foundation and your AI search visibility is significant. Go do them now while you have this post open.
If you are still deciding whether to use AIOSEO, this is what the plugin’s setup looks like once it is actually configured correctly, not the default out-of-the-box state. The configuration depth is part of what makes it worth paying for.
Get All in One SEO
Unlock advanced schema graphs, IndexNow integration, and automated crawler controls.
Frequently Asked Questions
Have lingering questions before deciding? Here are straight answers to the most common queries creators and site owners ask about AIOSEO:
Start with Organization schema and Author schema because these have the most direct impact on both Google E-E-A-T signals and AI search visibility. Then check your noindex settings to make sure tag archives and date archives are not consuming crawl budget. Those three alone account for the biggest gaps in most AIOSEO configurations.
Yes, through several settings. The sameAs links in Organization schema help AI systems verify your brand entity. IndexNow pings Bing on every publish, speeding up discovery by ChatGPT Search and Siri. The robots.txt editor lets you verify that AI crawlers including GPTBot and PerplexityBot have access to your content. The FAQPage schema builder in the post editor improves extraction probability for structured question and answer content across Perplexity, ChatGPT, and Google AI Overviews.
For most blogs, yes. Tag archive pages are low-value for search because they typically aggregate posts around a label that has no original content of its own. Setting tag archives to noindex prevents them from consuming crawl budget and eliminates the thin or duplicate content signal they can create in Google’s index. The exception would be a site where tag pages have been deliberately built out as content-rich destination pages, which is uncommon.
Open the post you want to add it to, scroll down to the AIOSEO meta box below the editor, click the Schema tab, and click Add Schema Graph. Select FAQ from the schema type options. Enter your question and answer pairs directly in the form that appears. Each answer should be complete in 40 to 80 words and self-contained. AIOSEO generates the FAQPage JSON-LD automatically and injects it into the page without any code required.
