Contact

Get in touch about the product, a defect, a security issue, or a factual error in something we have published. Each of those has a different route, and using the right one gets a faster answer.

Configuration placeholder. The contact addresses and form endpoint for this site have not been configured yet. Set them in the site's contact settings; until then, no email address, phone number or postal address is published here, because inventing one would be worse than leaving it blank.

Channels

• General and pre-sales questions — the general contact address, once configured.
• Support — the support address or the support form, once configured. Support is for people running the plugin.
• Bug reports — the support channel, using the checklist below.
• Security disclosures — the dedicated security address, once configured. Report privately and allow a reasonable period for a fix before disclosing. See [security](/security/).
• Corrections to an article — see below.

Reporting a bug

The more of this you include, the less of it we have to ask for:

• What you expected and what happened, in that order, and the exact wording of any error message.
• Steps to reproduce, from a known starting point. A defect we can reproduce is usually fixed; one we cannot usually is not.
• Versions — the SiteRank AI version, your WordPress version, your PHP version, and your database server and version.
• Environment — your host or local stack, whether the site is multisite, and whether an object cache or a page cache is in front of it.
• Other SEO plugins active — Yoast, Rank Math, All in One SEO, SEOPress, The SEO Framework or Slim SEO. Interoperability defects are common and this is usually the first question.
• Scale, if the problem involves a scan or a job: roughly how many posts and pages the site has.
• Screenshots of the screen where it went wrong, if it is a display problem.

Never send us a credential. Do not paste an API key, a password, a database dump or the contents of wp-config.php into a support message. We never need any of them, and the plugin's own diagnostics export is redacted before it is written for exactly this reason.

Reporting a factual error

If an article on this site states something incorrect, we want to know, and a correction supported by a primary source will be made quickly.

Send us the article URL, the specific sentence, and the source that shows it is wrong — the provider's own documentation or the relevant specification is the strongest form of this. How corrections are handled, and which are noted on the article itself, is set out in the editorial policy.

What we cannot help with

We do not audit sites for you, do not provide SEO consulting, and cannot tell you why an AI assistant did or did not mention your site — nobody can, and the methodology page explains why that question has no answer available from outside.