Most ByTheWeb features provide a specific message when a required connection, permission, credit balance, content setting, or WordPress condition prevents an action from completing.
This guide covers common troubleshooting situations for ByTheWeb AI and ByTheWeb GEO.
My API Key Will Not Save
Open:
ByTheWeb AI > API Connection & Credits
ByTheWeb AI verifies a new API Key before saving it.
The verification includes both:
- The API Key
- The current WordPress website domain
If verification fails, the new key is not saved.
“The entered API Key is invalid or does not match this website domain”
A ByTheWeb API Key is domain-specific.
This error means the key was not accepted for the current WordPress website domain.
Make sure you are using the API Key assigned to this exact registered domain.
An API Key belonging to another domain cannot be used for the current website.
For more information, see:
and:
Changing / Removing a Connected Domain
“The website domain could not be detected. The API Key was not saved.”
ByTheWeb AI detects the website domain from the current WordPress Site URL when verifying the API Key.
If the plugin cannot determine the domain, it does not save the new key.
Review the WordPress website URL configuration before attempting the API connection again.
“Communication error with the cloud server. Cannot verify the key right now.”
The API Key verification request could not complete successfully with ByTheWeb Cloud.
The plugin does not replace the currently stored API Key when this communication error occurs.
The connection can be attempted again when communication with the Cloud service is available.
If the error continues, see:
I Connected an API Key but an AI Feature Is Still Unavailable
Open:
ByTheWeb AI > API Connection & Credits
and confirm that the page recognizes the connected account and displays the information returned for the registered domain.
Depending on the account, this can include:
- Active Plan
- Credit Balance
- Monthly allowance
- Next Credit Reset
- Extra Credits
A stored API Key and an available credit balance are different requirements.
Cloud AI actions also require enough available credits for the requested paid action.
Perplexity or Claude Is Not Available in AI Audit
The current AI Audit provides:
- ChatGPT without an API connection
- Gemini without an API connection
- Perplexity with a connected ByTheWeb account
- Claude with a connected ByTheWeb account
If Perplexity or Claude is not enabled in the WordPress AI Audit screen, connect the domain’s API Key under:
ByTheWeb AI > API Connection & Credits
For more information, see:
The AI Audit Opens on ByTheWeb.ai
This is the expected workflow.
The AI Audit screen inside WordPress launches the ByTheWeb Website Scanner for the current website domain.
The complete report opens on ByTheWeb.ai in a new browser tab.
I See “Not enough credits”
ByTheWeb Cloud checks whether the connected domain has enough available credits before processing a paid AI action.
If there are not enough credits, the requested action cannot continue.
Open:
ByTheWeb AI > API Connection & Credits
to review the current balance.
Depending on the account, you can:
- Wait for the next monthly credit reset
- Purchase Extra Credits if the domain is eligible
- Select another available subscription package
For the current action costs, see:
For additional credit rules, see:
My Credits Ran Out but My Existing Content Is Still There
That is expected.
Running out of AI credits affects paid Cloud AI actions.
It does not automatically delete content already stored in WordPress.
Existing normal WordPress content such as:
- Posts
- Media Library images
- Saved image metadata
remains stored in WordPress.
Locally stored ByTheWeb data also remains in the WordPress database.
For the complete explanation, see:
My Subscription Ended but My Existing ByTheWeb Data Was Not Deleted
That is also expected.
Ending a trial, credit allowance, or subscription does not automatically delete locally stored website content.
If the relevant ByTheWeb plugin remains active, its supported local functionality can continue using locally stored data.
Cloud AI functionality that requires an eligible connection and available credits is a separate part of the system.
My FAQ Was Generated but It Is Not Visible on the Page
Stored FAQ data and visible FAQ display are separate.
ByTheWeb AI can store FAQ data and output supported FAQ / Q&A structured data.
To visibly display the FAQ on the frontend, use one of the supported display methods, such as:
- The ByTheWeb FAQ shortcode
- The ByTheWeb Elementor FAQ widget
For the available display options, see:
FAQ Shortcode & Elementor Widget
My FAQ Shortcode Is Not Using the Display Style I Expected
ByTheWeb AI includes FAQ frontend display settings.
The supported styles include:
- Standard
- Accordion
- Toggle
Open the FAQ settings and review the configured Display Style.
The shortcode display also uses the configured question heading and, for the Toggle style, the configured Toggle title and title tag.
FAQ Schema Exists but There Is No Visible FAQ Section
FAQ / Q&A structured data and visible FAQ HTML are not the same output.
FAQ data can exist in WordPress for structured-data purposes while the visible FAQ section is displayed separately through a supported frontend display method.
Use:
FAQ Shortcode & Elementor Widget
for the visible display workflow.
My AI Summary or Short Answer Is Saved but Not Visible on the Frontend
AI Summary and Short Answer are stored ByTheWeb GEO fields.
Displaying them on the frontend can use the supported ByTheWeb GEO shortcode or Elementor widget.
For the available output methods, see:
GEO Shortcodes & Elementor Widgets
AI Summary, Short Answer, FAQ or Schema Stopped Appearing After I Deactivated a Plugin
Plugin deactivation does not by itself delete the locally stored data.
However, functionality that depends on the plugin to register, render, or dynamically output that data is unavailable while the responsible plugin is inactive.
This can affect frontend output such as:
- AI Summary
- Short Answer
- FAQ display
- FAQ / Q&A structured data
- Other Schema generated by the plugin
- Plugin shortcodes and widgets
Normal WordPress content already created by ByTheWeb AI remains stored independently.
I Cannot See the ByTheWeb SEO Controls
First check whether Yoast SEO or Rank Math SEO is active.
ByTheWeb GEO intentionally does not expose or output its overlapping traditional SEO functionality when a supported external SEO provider is responsible for that functionality.
When Yoast or Rank Math is active, the external provider remains responsible for overlapping features such as:
- SEO titles
- Meta descriptions
- Canonical URLs
- Robots directives
- Core sitemap ownership
- Overlapping core Schema
ByTheWeb GEO continues providing its supported GEO functionality.
This is expected behavior, not an error.
I Activated Yoast or Rank Math and the ByTheWeb SEO Interface Changed
This is expected.
ByTheWeb GEO detects the supported active SEO provider and changes its behavior to avoid competing traditional SEO output.
The provider-aware integration is designed so Yoast SEO or Rank Math can continue owning their overlapping SEO functionality while ByTheWeb GEO remains responsible for its supported GEO layer.
My ByTheWeb XML Sitemap Is Not Being Used
ByTheWeb GEO’s own traditional SEO output is provider-aware.
If Yoast SEO or Rank Math SEO is active as the supported external provider, that provider remains responsible for overlapping sitemap functionality.
ByTheWeb GEO does not need to output a competing sitemap in that configuration.
If ByTheWeb GEO is the active SEO provider, its own XML Sitemap functionality applies.
For more information, see:
A Page Is Missing from the ByTheWeb Sitemap
ByTheWeb GEO applies sitemap eligibility rules before URLs are included.
Content can be excluded based on conditions such as:
- Noindex status
- Password protection
- The post type or taxonomy not being selected for sitemap inclusion
The sitemap settings include eligibility information for the selected post types and taxonomies.
When Yoast SEO or Rank Math SEO is active, that external provider is responsible for its own sitemap and indexability behavior.
My XML Sitemap Stopped Working After Activating or Deactivating an SEO Plugin
After activating or deactivating ByTheWeb GEO, Yoast SEO, Rank Math SEO, or another SEO configuration that changes the website’s sitemap and rewrite behavior, the XML Sitemap may occasionally stop loading correctly.
If this happens, refresh the WordPress permalink rules:
- Open WordPress Dashboard > Settings > Permalinks
- Do not change any permalink settings
- Select Save Changes
Saving the Permalinks page refreshes the WordPress rewrite rules.
After saving, check the XML Sitemap again.
This can be useful when a sitemap stops loading immediately after an SEO plugin has been activated, deactivated, or the active SEO provider has changed.
llms.txt or llms-full.txt Does Not Include a Page
ByTheWeb GEO does not automatically include every WordPress URL.
The LLM files use:
- The selected supported post types
- The selected supported taxonomies
- Indexability rules
- Individual LLM exclusions
- Public-content eligibility
Noindex and password-protected content is excluded.
Individual supported posts or taxonomies can also be excluded from the LLM files without necessarily being removed from the normal XML Sitemap.
For more information, see:
I Use Yoast or Rank Math and My llms.txt Eligibility Is Different
When Yoast SEO or Rank Math SEO is active, ByTheWeb GEO uses the supported external SEO provider’s indexability state when determining LLM eligibility.
This keeps LLM inclusion aligned with the active SEO provider instead of using a separate competing indexability decision.
I See a Warning About Another llms.txt Generator
ByTheWeb GEO detects supported situations where Yoast SEO or Rank Math may also be configured to generate an llms.txt resource.
The warning is intended to help identify competing LLM-file generators.
Review which system is configured to provide the website’s llms.txt endpoint rather than configuring multiple systems to compete for the same resource.
WordPress Is Set to “Discourage search engines from indexing this site”
The global WordPress search-engine visibility setting overrides individual ByTheWeb GEO indexing choices.
ByTheWeb GEO also applies this global state to its LLM-file robots behavior.
If the site is intentionally globally blocked from search engines, individual page-level Index settings do not override that global WordPress setting.
My robots.txt Changes Are Not Appearing
The ByTheWeb GEO Robots.txt AI Policy Manager is part of the ByTheWeb GEO SEO-provider functionality.
If Yoast SEO or Rank Math SEO is the supported active SEO provider, ByTheWeb GEO does not take over the overlapping traditional SEO layer.
When ByTheWeb GEO is responsible for the applicable robots.txt output, the final result can also be affected by:
- A physical
robots.txtfile - Cache plugins
- Security plugins
- Firewalls
- Server-level rules
For the complete feature behavior, see:
I Configured a Bot in Robots.txt but It Still Accessed the Website
The Robots.txt AI Policy Manager manages crawler directives in robots.txt.
It is not a security or access-control system.
Its purpose is to publish crawler policy directives for the configured user agents.
It should not be treated as protection for private or sensitive content.
I Expected ByTheWeb GEO to Output Its Own Organization, Article or Breadcrumb Schema Alongside Yoast or Rank Math
ByTheWeb GEO is provider-aware.
When Yoast SEO or Rank Math SEO owns the supported core Schema graph, ByTheWeb GEO integrates its supported enrichment with that provider instead of creating competing core entities for the same purpose.
The exact Schema output therefore differs between:
- ByTheWeb GEO as the SEO provider
- Yoast SEO as the provider
- Rank Math SEO as the provider
For more information, see:
A Custom Post Type Is Not Appearing in a ByTheWeb Feature
Not every ByTheWeb feature automatically applies to every registered custom post type.
Several ByTheWeb AI and ByTheWeb GEO features provide their own supported post-type or taxonomy selection settings.
Review the settings for the specific feature and confirm that the required content type is supported and enabled there.
For compatibility details, see:
I Cannot See API Connection & Credits
The API Connection & Credits administration page requires the WordPress manage_options capability.
A user without that capability will not have access to the API Key and credit-management screen.
For the complete access rules, see:
User Access Control & Permissions
I Cannot See a ByTheWeb AI Menu or Feature
Different ByTheWeb AI screens use different WordPress capabilities.
For example:
- Main ByTheWeb AI tools use content-editing capabilities
- Settings require broader editing capabilities
- API Connection & Credits requires
manage_options
The missing menu may therefore be the expected result for the current WordPress user’s role and capabilities.
My Subscription or Cloud Domain Was Removed but Local Features Still Work
The ByTheWeb Cloud account and the locally active WordPress plugins are separate parts of the system.
Removing Cloud access does not automatically deactivate the WordPress plugins or erase their locally stored data.
As long as the relevant plugin remains active, supported local functionality can continue using the local data already stored in WordPress.
For the complete distinction, see:
Changing / Removing a Connected Domain
When Should I Contact Support?
If the problem continues after checking the relevant condition described in this guide, contact ByTheWeb Support.
When contacting support, include information that identifies the problem clearly, such as:
- Which plugin is involved: ByTheWeb AI or ByTheWeb GEO
- The feature you were using
- The exact error message shown
- The website domain
- The installed plugin version
- A screenshot of the problem where useful
Use:
Where Should I Go Next?
For common product questions:
For API connection problems:
For credits and subscription behavior:
For account management:
Managing Your ByTheWeb Account
For direct assistance: