Setup guides
IndexNow on your platform
The key file has to live on your own site — that's how IndexNow proves you own it. How you put it there depends entirely on how your site is built. Pick yours.
CMS
WordPress
EasyAdd your IndexNow key file to WordPress without a plugin, or with one line in your theme.
Read the guide →Ghost
EasyAdd the key file to your theme's public assets folder.
Read the guide →Drupal
EasyDrop the key file in Drupal's document root — note that modern Drupal serves from /web, not the project root.
Read the guide →Ecommerce
Shopify
ModerateShopify blocks root-level files. Serving the key from a page template only covers /pages/, so full coverage needs Cloudflare in front.
Read the guide →WooCommerce
EasyWooCommerce runs on WordPress, so the key file goes in the WordPress root — and product changes are exactly what IndexNow is for.
Read the guide →Magento / Adobe Commerce
ModerateMagento serves from pub/, so the key file goes there rather than in the project root.
Read the guide →Framework
Hosting & CDN
Cloudflare
EasyServe the key file at the edge with a Worker or a Redirect Rule — no origin changes.
Read the guide →Netlify
EasyPut the key file in your publish directory and Netlify serves it from the root.
Read the guide →Vercel
EasyFiles in public/ are served from the site root on every Vercel deployment.
Read the guide →Server
Nginx
EasyOne location block serves the key file without touching your application.
Read the guide →Apache
EasyUpload the file to your document root, or serve it from .htaccess.
Read the guide →IIS / Windows Server
EasyCopy the file into wwwroot and make sure .txt is served as static content.
Read the guide →Website builder
Platform not listed?
If you can put a plain text file at the root of your site, IndexNow will work. Tell us what you're running and we'll write the guide.
Ask usStop waiting to be found
Set it up once. We keep telling the search engines about every change you make, for $12 a year.