The SEO category in AIUNIFY PROS SUITE currently contains four active subscriber-facing tools:
The current Sidebar routes these tools to:
/meta-description/keyword-research/seo-audit/schema-markupAll four are currently marked New in the Sidebar.
The shorter Sidebar labels open these full Tool pages:
The current subscriber source confirms that all four active SEO tools use the shared:
Standard AI Generator Workspace
None of the four uses a specialized SEO crawler, keyword database interface, ranking dashboard, or structured-data editor.
These Tools help generate:
They do not automatically perform the downstream SEO actions associated with those outputs.
Generating SEO content or recommendations does not guarantee:
Search-engine performance depends on many factors outside these Tool pages.
The current SEO category does not provide subscriber controls for:
Generated SEO material should be checked for:
before implementation.
The source verifies the following four active entries:
Sidebar Tool ID:
meta-description
Route:
/meta-description
Sidebar Tool ID:
keyword-research
Route:
/keyword-research
Sidebar Tool ID:
seo-audit
Route:
/seo-audit
Sidebar Tool ID:
schema-markup
Route:
/schema-markup
Each current active SEO Sidebar entry contains:
isNew: true.
Unlike certain Legal tools documented in Chapter 39, none of the four current SEO Sidebar entries is marked isPro: true.
General subscription, Tool assignment, Token, and system availability rules can still apply.
The feature catalogue also contains commented references for:
These are not current active feature entries in the subscriber SEO catalogue.
A source reference exists for:
Title Tag Generator
but it is commented out.
Do not expect it as a current SEO Sidebar Tool.
The feature catalogue contains a commented:
Content Brief
reference.
It should not be documented as an active subscriber Tool in the current version.
A commented:
Alt Text Generator
reference exists, but it is not part of the current active SEO feature list.
A Backlink Outreach feature is also commented out.
The current Knowledge Base should follow what the subscriber can actually access through the active Sidebar rather than every feature name that appears somewhere in source.
All four active SEO Tools use Standard ToolPage.
The shared page redirects unauthenticated users toward:
/login.
Each SEO Tool displays:
The left-side Card is:
Input
Current shared wording:
Describe what you want to generate.
Each SEO Tool uses a single natural-language Textarea.
There are no dedicated structured fields for:
unless the Tool's Prompt asks the subscriber to describe those details manually.
Each of the four SEO Tools provides its own Prompt guidance.
Those exact placeholders are documented later in this chapter.
Select:
Generate
to submit the request.
During the AI response:
Generating...
appears on the button.
The shared Generate button is disabled if the Prompt is empty.
Subscribers can also use:
Ctrl + Enter
inside the Prompt Textarea.
Current message:
Input required
with:
Please enter a prompt to continue.
Each SEO Tool includes three examples.
Selecting an example places that text into the Input field.
Generation does not start until the subscriber submits it.
Standard ToolPage instructs the selected Model using:
“You are a helpful AI assistant for the tool: [title]. [description]”
and then provides the subscriber Prompt.
Their outputs are generated by the selected AI Model.
They are not automatically produced by a specialized external SEO database.
Each SEO request passes its Tool ID through the shared streaming function.
meta-description
keyword-research
seo-audit
schema-markup
Standard SEO Tools use the current subscriber-selected AI Model.
Configured subscriber AI provider API Keys can also be passed through the shared generation pathway as documented in Chapter 11.
The right-side Card is:
Output
with:
Generated content will appear here.
Results appear progressively as AIUNIFY receives the generated response.
The Output is displayed through the shared Markdown renderer.
This can display:
depending on the response.
When Output exists, a Copy action appears.
Current message:
Copied!
with:
Content copied to clipboard.
A Download action is also provided.
Standard ToolPage saves:
.txt
files.
Current pattern:
meta-description-output.txt
Current pattern:
keyword-research-output.txt
Current pattern:
seo-audit-output.txt
Current pattern:
schema-markup-output.txt
Keyword Research does not provide a dedicated CSV export.
None of the four SEO Tools has source-verified spreadsheet export.
SEO Audit uses the standard .txt Download.
Schema Markup Generator also downloads Standard ToolPage text rather than a dedicated .json or .jsonld file.
Standard SEO Output is not directly editable inside the Tool.
There is no persistent Save button.
No source-verified persistent history is provided by Standard ToolPage.
There is no:
workflow.
The Standard Reset control clears:
and returns focus to the Input Textarea.
Copy or Download useful output before Resetting or replacing it with another generation.
Standard ToolPage determines Base Cost through:
The Tool Header displays:
[amount] tokens per use
plus the subscriber's current Token balance.
If the selected Model is categorized as OpenAI, Standard ToolPage applies the current:
1.5×
display multiplier, rounded upward.
If the live subscriber interface displays a different cost than a static Knowledge Base value, use the amount displayed in the live Tool.
| SEO ToolCurrent Catalogue ReferenceRoute Fallback | ||
| Meta Description | 10 Tokens | 10 |
| Keyword Research | 20 Tokens | 20 |
| SEO Audit | 30 Tokens | 30 |
| Schema Markup | 20 Tokens | 20 |
The current feature catalogue and individual routes agree on these values.
10 Tokens
20 Tokens
30 Tokens
20 Tokens
Navigate to:
Sidebar → SEO → Meta Description
Route:
/meta-description
Full page title:
Meta Description Generator.
Current description:
Create compelling meta descriptions that improve click-through rates.
Current guidance:
Enter your page title and main content topic...
Meta description for a digital marketing services page
Product page description for running shoes
Blog post meta about healthy meal prep.
Current Base Reference:
10 Tokens
Include the actual Page Title or intended subject.
Describe what the page is genuinely about.
If a specific search phrase matters, include it in the Prompt.
Explain what the searcher is trying to accomplish where relevant.
Examples:
Describe who the page is meant to attract.
Tell the Tool what makes the page, Product, or Service worth clicking.
Examples:
You can ask the AI to include an appropriate action phrase.
There is no dedicated Quantity selector.
Use the Prompt.
Example:
Generate five distinct Meta Description options.
The current page does not provide a structured Character Limit input.
There is no source-verified live Character Counter beneath the generated Meta Description.
The Tool does not programmatically verify how a particular Search Engine will truncate the generated text.
If you have a target Character range, state it in the Prompt.
Even if you publish a Meta Description, search engines can display different snippet text depending on the Query and indexed content.
The Tool cannot guarantee the exact SERP snippet shown.
The Tool does not automatically fetch the Website page being optimized.
The page uses the Standard Textarea rather than a dedicated URL input.
It does not source-verify reading the current <meta name="description"> from a live page.
It does not crawl a Website to find duplicate Meta Descriptions.
There is no visual Google-style search-result Preview.
The Tool does not calculate:
The page description says the Tool creates compelling Meta Descriptions that improve click-through rates.
That description should not be interpreted as a guarantee of measurable CTR improvement for every generated result.
Generated copy should accurately summarize what users will find after clicking.
Do not promise information, Products, or results that the Landing Page does not provide.
Avoid forcing a Keyword into unnatural language.
Do not automatically reuse one Description across multiple unrelated pages.
Mention a meaningful value proposition where appropriate.
Title and Meta Description should work together rather than duplicate each other word-for-word.
Use Copy or Download before generating new variations.
Navigate to:
Sidebar → SEO → Keywords
Route:
/keyword-research
The current workspace is:
Keyword Research Assistant.
Current description:
Discover relevant keywords and search terms for your content.
Current guidance:
Enter your topic or niche to find keyword opportunities...
Keywords for a personal finance blog
SEO keywords for a yoga studio website
Long-tail keywords for email marketing software.
Current Base Reference:
20 Tokens
Start with the main subject.
Narrow the market where possible.
Tell the Tool whether the content supports:
Describe the user searching for the content.
For local or regional SEO, specify:
where relevant.
You can request Keywords by intent stage, such as:
The built-in Email Marketing example specifically demonstrates long-tail Keyword prompting.
You can request question-style phrases.
Example:
“What is CRM software?”
For local businesses, request combinations involving:
For E-Commerce, include:
You can request phrases related to:
Describe the customer Problem and request search phrases associated with solving it.
There is no Quantity selector.
State the desired number.
Ask the Tool to organize Keywords by:
Keyword Research Assistant is a Standard ToolPage.
The current client sends:
to the AI streaming system.
The subscriber page does not establish a connection to a live Keyword-volume provider.
The Tool does not source-verify an authenticated Google Keyword Planner integration.
There is no current subscriber workflow to import actual Search Console Queries.
The page does not establish live Google Trends retrieval.
No Ahrefs integration is source-verified in this Tool.
No Semrush integration is source-verified.
No Moz Keyword data connection is established.
The current source does not verify real-time Monthly Search Volume retrieval.
It does not source-verify current advertising Cost Per Click.
The Tool does not expose a source-verified advertiser competition metric.
There is no source-verified Keyword Difficulty database or scoring algorithm on this page.
The Tool does not determine where your Website currently ranks for each generated Keyword.
It does not automatically crawl competitor sites and extract their ranking Queries.
If the AI response invents or estimates values such as:
those values should not be presented as source-verified live Keyword data.
The strongest source-verified use is:
Keyword and Search-Term Idea Generation
Before large SEO investments, verify demand using appropriate current SEO/search data sources.
Search Intent often matters as much as the Keyword itself.
Ask the Tool to separate:
Generated Keywords are planning inputs.
They should not all be forced unnaturally into one page.
Choose a coherent primary topic and related supporting terms.
You can ask AI to recommend which Keywords fit:
Do not present AI-generated Keyword estimates as measured search-engine data.
Current filename:
keyword-research-output.txt
Navigate to:
Sidebar → SEO → SEO Audit
Route:
/seo-audit
The full workspace title is:
SEO Audit Checklist.
The Sidebar label is:
SEO Audit
but the page itself is specifically titled:
SEO Audit Checklist.
This difference is important to understanding what the current Tool actually does.
Current description:
Generate comprehensive SEO audit checklists for websites.
Current guidance:
Enter your website URL or describe your site type...
Complete SEO audit checklist for an e-commerce site
Technical SEO checklist for a WordPress blog
Local SEO audit for a restaurant website.
Current Base Reference:
30 Tokens
The source explicitly identifies the Tool as:
SEO Audit Checklist
and describes its purpose as generating checklists.
Although the placeholder says:
Enter your website URL
the Tool still uses Standard ToolPage.
The subscriber's Input string is passed directly to the AI generator.
The current page source does not add a separate Website fetch, crawler, scraper, or browser-control operation before generation.
Therefore:
Entering a URL into SEO Audit should not be described as a source-verified live Website crawl.
A URL can serve as Context in the Prompt.
However, the inspected subscriber source does not establish that the Tool visits the URL and reads the page.
Use the Tool to generate a:
Website-Type-Specific SEO Audit Checklist
that you or another auditing system can apply to the Website.
You can request checklist items concerning:
You can request review areas involving:
Ask the checklist to cover Sitemap review.
Request robots.txt review steps.
Include Canonical review where relevant.
Ask for checks involving:
A checklist can remind the subscriber to inspect broken links.
The Tool itself does not source-verify crawling the Website to identify them.
Request checks for secure Site configuration.
A comprehensive checklist can include Mobile review.
The Tool does not itself run a device lab.
You can request Page Speed checks.
The page does not source-verify a live Lighthouse or PageSpeed Insights test.
You can request checks related to Core Web Vitals.
The Tool does not retrieve source-verified live field data from the inspected subscriber page.
Request review of Title relevance and uniqueness.
Request review of Meta Description quality and duplication.
Checklist items can cover:
Ask for review of:
Request internal-link review.
Checklist items can cover:
Request URL naming and hierarchy review.
Ask the audit to evaluate whether pages satisfy expected user intent.
Include checks for duplicated or highly similar pages.
Request criteria for identifying pages that provide insufficient value.
Ask for review of outdated content where appropriate.
Request analysis questions about missing topic areas.
The built-in Restaurant example confirms local SEO is an intended checklist use case.
Ask the checklist to review local listing consistency.
Review consistency of:
where appropriate.
Ask for location-page review.
A local SEO checklist can include review-management considerations.
The Tool includes a built-in E-Commerce Audit Checklist example.
Request checks for:
Ask for category-page optimization checks.
For larger stores, request review criteria for filter/facet indexing.
Request checks for handling discontinued or out-of-stock Products where relevant.
The current Tool does not source-verify crawling the Website.
It does not automatically count indexed or crawlable pages.
It does not generate a source-verified list of broken URLs from a live crawl.
It does not retrieve actual:
responses from Website pages through the inspected SEO Audit page.
The Tool does not automatically fetch and parse a live robots.txt file.
It does not automatically retrieve XML Sitemaps.
No source-verified Search Console or Chrome UX Report data is retrieved.
The subscriber page does not source-verify launching Google Lighthouse.
There is no direct Search Console authorization/import workflow.
The Tool does not import Website traffic data.
It does not retrieve a live backlink profile.
It does not track current Keyword positions.
It does not automatically audit a competitor Website.
The Tool does not modify Website Code, Content, Titles, Metadata, or Server settings.
A generated Checklist describes what to inspect.
Actual Website conditions must still be measured or verified.
Examples:
If useful, state whether the Website uses:
Examples:
Ask for:
priority items.
You can ask AI to classify recommendations by:
For example:
Technical → On-Page → Content → Local → Off-Page
A strong workflow is to provide findings from actual SEO tools and ask AIUNIFY to:
A checklist item such as:
Check for duplicate Titles
does not mean duplicate Titles actually exist.
Current filename:
seo-audit-output.txt
Navigate to:
Sidebar → SEO → Schema Markup
Route:
/schema-markup
Full workspace title:
Schema Markup Generator.
Current description:
Generate structured data markup for rich search results.
Current guidance:
Describe the content type and details for schema markup...
Schema for a local business with hours and reviews
Product schema for an e-commerce item
Article schema for a blog post.
Current Base Reference:
20 Tokens
Schema Markup Generator produces AI-generated structured-data markup based on the subscriber's Prompt.
The Tool's page does not enforce a dedicated Schema editor.
If you need:
JSON-LD
request it explicitly.
Example:
“Generate valid JSON-LD Schema.org markup for this local business.”
Specify the intended Schema Type.
The first built-in example confirms Local Business as an intended use case.
The second built-in example confirms Product markup as an intended use case.
The third built-in example confirms Article markup as an intended use case.
Provide the correct Business Name.
Provide accurate address information if appropriate.
Supply the correct phone number.
Provide actual business hours.
Include the correct URL.
Describe the appropriate business category.
If review information is included, use real and supportable review data.
Do not instruct AI to fabricate ratings.
Use the real Product Name.
Use an accurate Product description.
Provide the real Brand.
Use the actual current Price.
Supply the correct Currency.
Use the actual Product availability status.
Provide real identifiers where appropriate.
Only include ratings/reviews that accurately reflect real data.
Provide the actual Headline.
Use the correct Author.
Use the actual Date.
Provide an accurate modification Date when used.
Use the actual Publisher.
Provide the correct Image URL where appropriate.
There is no Type dropdown followed by structured field inputs.
Everything is entered through Standard ToolPage's Prompt.
The page does not source-verify running generated output through a structured-data validator.
There is no source-verified direct Google Rich Results Test connection.
No external Schema.org validation workflow is established by this Tool page.
The Tool does not add the generated markup to a Website.
It does not automatically update:
It does not place JSON-LD inside:
<script type="application/ld+json">
in Website Code automatically.
The Tool does not crawl a page to see which structured-data markup is already present.
It does not determine whether multiple conflicting Schema blocks already exist.
Valid Schema markup does not guarantee a Search Engine will display a Rich Result.
The Tool's description says it generates structured data markup for rich search results.
Search engines independently decide whether eligible enhancements appear.
The Tool cannot approve markup on behalf of Google, Bing, or another search engine.
Structured Data should represent visible and truthful Website content.
Do not create fake:
data merely to make markup appear richer.
If Product data changes, structured data can become outdated.
The markup should correspond to what users can actually see or access where required.
After generation, use an appropriate current validation workflow before deployment.
Once implemented, test the live Website rather than only the generated draft.
Search-engine structured-data reports, where available, should be reviewed separately.
Current filename:
schema-markup-output.txt
| CapabilityMeta DescriptionKeyword ResearchSEO AuditSchema Markup | ||||
| Standard ToolPage | Yes | Yes | Yes | Yes |
| Prompt Input | Yes | Yes | Yes | Yes |
| Example Prompts | Yes | Yes | Yes | Yes |
| Selected AI Model | Yes | Yes | Yes | Yes |
| Provider API Keys | Yes | Yes | Yes | Yes |
| Streaming Output | Yes | Yes | Yes | Yes |
| Copy | Yes | Yes | Yes | Yes |
| TXT Download | Yes | Yes | Yes | Yes |
| Direct Edit | No | No | No | No |
| Save | No | No | No | No |
| Persistent History | No | No | No | No |
| FunctionSource-Verified in Current Tool? | |
| Generate Meta Description copy | Yes |
| Generate Keyword ideas | Yes |
| Generate SEO Audit checklist | Yes |
| Generate Schema Markup text | Yes |
| Live Search Volume | No |
| Live CPC | No |
| Live Keyword Difficulty | No |
| Live SERP rankings | No |
| Website crawling | No |
| Broken-link crawling | No |
| Search Console import | No |
| Google Analytics import | No |
| Core Web Vitals retrieval | No |
| Schema validation | No |
| Automatic Website modification | No |
| SEO ActionAutomatically Performed? | |
| Write Meta Description | Yes, as generated text |
| Add Meta Description to Website | No |
| Suggest Keywords | Yes |
| Add Keywords to Website | No |
| Generate Audit Checklist | Yes |
| Crawl Website | No |
| Fix SEO Issues | No |
| Generate Schema Draft | Yes |
| Add Schema to Website | No |
| Validate Schema | No |
| Submit Sitemap | No |
| Request Indexing | No |
| Track Rankings | No |
Identify Page
→ Identify Primary Search Topic
→ Identify Search Intent
→ Identify Unique Value
→ Generate Several Meta Description Options
→ Review for Accuracy
→ Select Final Version
→ Add It to the Website Through the Appropriate CMS/Code Workflow
→ Monitor Search Performance Separately
Define Topic
→ Define Audience
→ Define Geography
→ Generate Keyword Ideas
→ Group by Search Intent
→ Group into Topic Clusters
→ Validate Important Keywords With Current Search Data
→ Map Keywords to Pages
→ Create/Optimize Content
→ Measure Performance Separately
Describe the Website
→ Generate SEO Audit Checklist
→ Use Actual Crawling/Analytics/Search Data to Check Each Item
→ Document Confirmed Issues
→ Prioritize Issues
→ Implement Fixes
→ Re-Crawl/Re-Test
→ Measure Search Performance
Identify Page Type
→ Select Appropriate Schema Concept
→ Provide Accurate Page Facts
→ Generate JSON-LD/Markup Draft
→ Review All Properties
→ Validate With Appropriate Structured-Data Tools
→ Add to Website
→ Test the Live Page
→ Monitor Search-Engine Reports Separately
Enter non-whitespace Prompt text.
Provide more context.
Examples:
Standard ToolPage does not provide an Edit mode.
Copy the result into an editor.
No persistent Standard SEO history is source-verified.
The current Standard Download is .txt.
SEO Audit also uses .txt.
.jsonThe Standard Download remains .txt.
Copy the generated code into the appropriate file or Website implementation workflow.
Request a specific Character range and regenerate or edit externally.
Ask for a fuller value proposition while maintaining your desired length.
Provide more accurate Page content context.
The current Tool has no visual SERP Preview.
The current Tool does not source-verify fetching the live Page.
Provide the current Meta Description manually if you want it revised.
The current Tool is an AI Keyword ideation assistant rather than a source-verified live Keyword database.
Current live CPC retrieval is not established by this page.
The Tool does not source-verify a current Difficulty metric.
Competitor SERP data is not automatically retrieved.
There is no current Search Console import in this workspace.
Add:
to narrow the Prompt.
That is consistent with the current implementation.
SEO Audit is a Standard AI generator titled:
SEO Audit Checklist
and does not source-verify fetching the URL.
Use an appropriate live Website crawler.
The current AIUNIFY Tool can help structure a checklist or analyze data you provide.
The current SEO Audit page does not source-verify executing a PageSpeed or Lighthouse test.
The Tool does not retrieve Google index counts.
A ranking tracker is not part of this Tool.
The Tool generates recommendations/checklists; it does not alter the Website.
Explicitly request:
JSON-LD
in your Prompt.
Provide the missing:
and regenerate.
The current Tool does not provide a source-verified validator.
Use an appropriate validation workflow after generation.
Implementation must occur separately through your Website's Code or CMS.
Generating and implementing Schema does not guarantee a Search Engine will show a Rich Result.
Avoid presenting AI-generated:
as measured data unless independently verified.
Structured Data should reflect actual review information.
Business hours, addresses, phone numbers, Prices, and Product availability should be real.
A generated Audit Checklist is a list of things to inspect.
It is not proof that each issue exists.
Neither the Tool nor the subscriber should present an AI-generated SEO plan as a guaranteed ranking outcome.
The final approved Description must be added through:
The final approved markup must be added to the Website through an appropriate development/CMS workflow.
Keywords are strategic inputs.
Modern SEO does not require a subscriber to place every generated Keyword everywhere on a page.
Confirmed Audit findings must be addressed through:
as appropriate.
A practical workflow is:
Generate Keyword Ideas
→ Select the Page's Primary Search Theme
→ Use Meta Description Generator
If an actual audit identifies missing structured data, Schema Markup Generator can help draft the markup.
There is no automatic Tool-to-Tool handoff.
If an audit identifies weak or missing Descriptions, use Meta Description Generator separately.
Generated Keyword ideas can be carried into AIUNIFY's Writing or Marketing tools where appropriate.
No current automatic transfer is source-verified.
For actual performance, you need real measured data from an appropriate source.
AI-generated text is not measured Search Impressions.
The SEO Tools do not retrieve actual organic Click counts.
No live average Search position is source-verified.
Meta Description Generator does not retrieve actual Search CTR.
The SEO category does not retrieve measured Website Sessions.
No organic Conversion tracking is implemented in these Tool pages.
No live Backlink database is connected.
Understand what the target user wants.
SEO copy should support genuinely useful content rather than merely containing Keywords.
Search optimization should not come at the cost of factual accuracy.
AI can produce outdated, generic, or unsuitable recommendations.
Structured Data and other technical modifications should be tested before production use.
Actual results should be evaluated using real search and Website data.
SEO is an ongoing process rather than a one-time generation.
Meta Description Generator currently supports:
It does not establish:
Keyword Research Assistant currently supports:
It does not establish:
SEO Audit Checklist currently supports:
It does not establish:
Schema Markup Generator currently supports:
It does not establish:
.json exportThe current SEO catalogue uses:
Unlike several Tools documented in earlier chapters, the four active SEO Tools currently have no route-vs-catalogue Token discrepancies in the inspected source.
A live aiLimits configuration can override the catalogue value through Standard ToolPage.
SEO Prompts do not require:
Provider API Keys should be configured through the dedicated AIUNIFY API-Key workflow rather than inserted into SEO Prompt content.
If entering a URL into SEO Audit, remember that the current Tool treats it as Prompt text rather than source-verified live crawl input.
Only provide proprietary research if doing so complies with your organization's policies.
AIUNIFY PROS SUITE currently exposes four active SEO Tools:
All four are marked New in the current Sidebar and none is currently marked Pro.
The current SEO category does not contain a specialized SEO workspace.
All four active Tools use AIUNIFY's Standard ToolPage and therefore share:
Input → Generate → Streaming Markdown Output → Copy → TXT Download
Meta Description Generator creates AI-written Meta Description copy from Page Title and Topic context.
Its current built-in examples cover:
and its current Base Reference is 10 Tokens.
The Tool does not crawl a Page, inspect current Metadata, enforce a Character limit, provide a SERP Preview, or guarantee search CTR.
Keyword Research Assistant generates Keyword and Search-Term ideas from a Topic or Niche.
Its built-in examples cover:
and its current Base Reference is 20 Tokens.
The current subscriber source does not establish connections to Google Keyword Planner, Google Search Console, Google Trends, Ahrefs, Semrush, Moz, or another live Keyword database. Consequently, generated Keyword ideas should not be described as source-verified live Search Volume, CPC, Keyword Difficulty, or ranking data.
The Sidebar says SEO Audit, but the actual page title is:
SEO Audit Checklist.
The page is explicitly designed to generate comprehensive SEO Audit checklists for Websites and provides examples for:
Its current Base Reference is 30 Tokens.
Although the placeholder permits a Website URL, Standard ToolPage simply sends the subscriber Input to the AI generation pathway. The current source does not establish a separate Website crawl or URL-fetch operation. Therefore, the correct subscriber expectation is:
SEO Audit generates an AI audit checklist; it is not currently a source-verified live crawler.
Schema Markup Generator creates structured-data drafts based on subscriber-provided content details.
Its current built-in examples cover:
and its current Base Reference is 20 Tokens.
The Tool does not independently validate generated Schema, insert it into a Website, retrieve existing Schema, connect to a CMS, or guarantee Rich Results.
The shared feature catalogue also contains commented references for:
These should not be presented as current active subscriber SEO Tools.
Current Base References are:
The current route and feature-catalogue values agree. Standard ToolPage can still apply a live AI-limit override and its selected-Model cost rules.
The central operating principle for Chapter 40 is:
AIUNIFY PROS SUITE SEO Tools accelerate SEO copywriting, Keyword ideation, Audit planning, and Structured Data generation. They do not currently replace live Search Console data, Keyword databases, Website crawlers, performance testing, ranking trackers, structured-data validators, or the Website-development work required to implement and measure SEO changes.