wp-config constants

The wp-config.php constants RankKit SEO reads, the ones it defines for your code, and the WordPress constants that change its audit and IndexNow behavior.

Updated 2 min read
On this page

RankKit SEO is configured in wp-admin, not in wp-config.php. A handful of constants still matter: a few you can set, some RankKit SEO defines for your own code, and some WordPress constants it reads.

Add constants to wp-config.php above the line /* That's all, stop editing! Happy publishing. */.

Constants you can set

Constant Default What it does
SPEEDRANK_FS_ID 42293 The Freemius product ID used for licensing and updates.
SPEEDRANK_FS_PUBLIC_KEY RankKit SEO's public key The Freemius public key that goes with the product ID.

Important Leave SPEEDRANK_FS_ID and SPEEDRANK_FS_PUBLIC_KEY alone on normal sites. Both are public values that RankKit SEO sets for you. If either is empty, the licensing SDK isn't loaded and the plugin runs as RankKit SEO Free, without license activation, the trial or Pro updates.

Constants RankKit SEO defines

These are set by RankKit SEO when it loads. Read them in your code; don't define them yourself.

Constant Value
SPEEDRANK_VERSION The plugin version, for example 1.1.1.
SPEEDRANK_DB_VERSION The database schema version.
SPEEDRANK_FILE Full path to the main plugin file.
SPEEDRANK_DIR Path to the plugin folder, with a trailing slash.
SPEEDRANK_URL URL of the plugin folder, with a trailing slash.
if ( defined( 'SPEEDRANK_VERSION' ) && version_compare( SPEEDRANK_VERSION, '1.1.0', '>=' ) ) {
	// Code that needs RankKit SEO 1.1.0 or later.
}

WordPress constants RankKit SEO reads

Constant Where RankKit SEO uses it
DISALLOW_FILE_EDIT The site audit security check "Theme and plugin file editing is enabled" passes when it is true. When you apply that check's fix, RankKit SEO defines DISALLOW_FILE_EDIT as true on every request (unless wp-config.php already defines it). See Security hardening.
WP_DEBUG, WP_DEBUG_DISPLAY The audit warns "PHP errors are shown to visitors" when debug output reaches the page. Set WP_DEBUG_DISPLAY to false on live sites.
WP_DEBUG_LOG When it is true and wp-content/debug.log exists, the audit checks whether the log can be downloaded ("The debug log can be downloaded by anyone").
WP_IMPORTING While it is true (during imports), publishing a post doesn't trigger an IndexNow submission.

Recommended settings for a live site:

define( 'WP_DEBUG', false );
define( 'WP_DEBUG_DISPLAY', false );
define( 'DISALLOW_FILE_EDIT', true );

FAQ

Can I set RankKit SEO's settings in wp-config.php?

No. Settings are stored in the database and changed in RankKit SEO → Settings, by AI agents (within their permissions) or through backups and export and import.

Can I turn off AI agent access with a constant?

No. Turn off Allow AI agents to connect in RankKit SEO → AI Agents. Agents can't turn it back on themselves.

Was this page helpful?

Still need help?

Email us with your WordPress and RankKit SEO versions and what you tried. Pro customers get priority replies.

Contact support