RankSense has the ability to make the following types of SEO changes:
Meta robots tags (index, follow, noindex, nofollow)
404 error fixes (a special type of 301 redirect rules)
Media alternate tags
Image alt text
Bot traps (a special type of rel="nofollow" rules)
Find and Replace
Important: RankSense will overwrite the robots.txt, HTML meta tags, and existing 301 redirects, if they are present. This overwriting occurs on the Cloudflare layer, so the origin is unaffected.
We control these changes with a spreadsheet that we call a “rules sheet,” because they provide “rules” for our app. There are templates for rules sheets here: Rules sheet template
There is a different template for each type of SEO rule. You can make a copy of the sheet to fill in with your SEO rules. The sheets contain examples, so be sure to delete unwanted rules before publishing. Please note that each sheet can contain a maximum of 10,000 URLs.
Please note that each template sheet has a tab name which tells the software which type of rule it is. If you copy the headings to a new Google Sheet, but the tab name does not match, the app will not recognize the type of rule. A typo in the tab name will also cause it to fail. The names of the tabs are:
robots (for meta robots tags such as noindex, not to be confused with robots.txt)
redirects (for 301 redirects that are not associated for 404 URLs)
errors (for 301 redirects for 404 URLs, please read below for details)
images (for image alt text)
bot_traps (for a special type of rel="nofollow" rules)
RankSense supports an advanced feature that allows you to track the impact of the SEO changes you make. For more on this feature, visit How to tag SEO changes to gain insights. If you wish to tag your SEO changes, we recommend creating a separate Google Sheet for each type of change. Be sure to use the exact column names and tab names that are found in the template sheet.
This article only covers how to create the rules. For how to publish them, please see the article, “How to publish SEO solutions on RankSense.”
URL-based rules vs site-wide rules
Most of the rules in RankSense are “URL-based.” These are rules where a given change will be made on the URL listed. An example of a type of URL-based rules are meta title changes. The URL is indicated in the first column, the new title is indicated in the second column.
URL-based rules can accept wildcards in the first column, so that every URL that matches the wildcard pattern will be changed.
In contract, there are some types of rules that are “site-wide.” They effect the entire site. These include:
Image alt text - Everywhere that a given image is found, the alt tag that is specified will be applied.
Robots.txt - These are considered a type of “site-wide” rules.
This sheet is used to add a canonical tag to a page. It will also overwrite the existing canonical tag, if present.
Formatting: In the first column, add the URL that the canonical tag will be applied to. In the second column, add the canonical URL (i.e. the URL that should be inside the canonical tag).
The robots sheet is used to add index, follow, noindex and nofollow meta robots tags, or overwrite existing tags.
Formatting: In the first column, add the URL that the meta robots tag(s) should be applied to. In the second column, add the desired tag(s), separating with a comma and space if you use more than one tag. Please see the template for examples.
The tags here will overwrite all meta robots tags on the existing page. If the existing page has an “index” tag, and you wish to add a “follow” tag, you should include the text “index, follow” in the second column, not just “follow” (do not include quotation marks on the sheet).
This sheet is used to add or overwrite meta titles.
Formatting: Place the URL in the first column, and the desired meta title in the second column.
This sheet is used to add or overwrite meta descriptions.
Formatting: Place the URL in the first column, and the desired meta description in the second column.
This sheet is used to modify an existing h1 on the page – the first one that appears in the HTML.
Formatting: Place the URL of the page you wish to modify in the first column, and the desired h1 in the second column.
This sheet is used to specify hreflang tags for sites that are available in more than one language or country (i.e. a US site and a UK site; or an English and Spanish site within the US).
Formatting: Place the URL of the page you wish to modify in the first column. You will need to use the same URL on multiple lines in order to specify multiple hreflang tags.
In the second column, place the hreflang attribute. For example, “en” for English, “es” for Spanish, “en-us” for English users in the US, etc. You can also specify “x-default” for the default page. Do not enter quotation marks in this column.
In the third column, specify the URL for the language and/or country that you listed in the second column.
This sheet adds 301 redirects to URLs that are currently 404 status. We differentiate these from “redirect” rules (see below) because the rule will automatically be deactivated in the URL becomes 200 status again at the origin.
Formatting: In the first column, place the 404 URL. In the second column, place the URL that it should redirect to. In the third column, place the status code to apply (typically 301).
This sheet adds 301 and 302 redirects, and is intended to be used for URLs that are currently 200 status.
Redirect rules should be used very carefully because RankSense rules overwrite what is present on the site’s server, so if redirect rules are created for URLs that should be 200 status, it will create a problem on the site that can impact users as well as SEO.
Redirect rules cannot be used for sitewide redirects, i.e. to redirect all non-www URLs to their www equivalents. Sitewide redirects should be implemented on the server.
Formatting: In the first column, place the URL that should be redirected. In the second column, place the URL that it should redirect to. In the third column, place the status code to apply (typically 301 or 302).
This sheet adds alternate media tags for sites that have a separate mobile site, i.e.
<link rel="alternate" media="handheld" href="https://m.example.com">. Please note that the mobile site will need to be set up separately and handled with a separate rules sheet from the desktop site.
Formatting: The first column contains the URL you wish to modify. The second column contains the media attribute (i.e. “handheld”, but do not enter quotation marks on the sheet). The third column contains the URL to specify as the alternate.
The robots_txt sheet is used to publish a new robots.txt file or overwrite the existing one. It does not add to the existing robots.txt. Any line that is present on the current robots.txt must be transferred to the sheet or it will be removed when you publish.
Formatting: The first column on the sheet should contain anything that comes before the colon on a normal robots.txt file. The second column should contain anything that comes after the colon. The colon and space will be added for you! See the template for an example.
Images (image alt text)
The images sheet is used to add alt text to an image (or replace the existing alt text. This is one of the types of site-wide rules. Everywhere the image is found on the site, the alt text will be applied.
Formatting: The first column on the sheet contains the URL of the image. The second column contains the desired alt text.
This sheet is used to create bot traps rules. Bot traps (also known as crawler traps) are sets of infinite pages that search engine bots can get stuck crawling. This eats up the crawl budget and prevents the bots from finding the unique content on the site. An example of a bot trap is a site that has many faceted navigation parameters that can be combined to create thousands (or millions) of possible URLs.
In RankSense, bot traps rules are used to add rel=“nofollow” to links. (Not to be confused with the nofollow meta tag, which can be applied using robots rules.)
Because these are a sitewide rule, the nofollow will be added wherever the link occurs on the site. These rules also support wildcards, so the nofollow can be added to all links that follow a pattern.
Bot traps rules can also be used to apply rel=“sponsored” and rel=“ugc” to links, wherever they occur on the site.
Please note that Google has announced that these three link attributes (nofollow, sponsored and ugc) will be treated as “hints” by Googlebot as of March 1, 2020. See their blog post for more information.
Formatting: On the bot_traps tab, the first column is the URL that should have a nofollow attribute applied wherever that link occurs on the site. This column accepts wildcards. The second column should contain the specific attribute you wish to apply (nofollow, sponsored or ugc).
This pages sheet template is used to create specific rules for the pages. Page(s) rules are used to customize your page(s). They give you the ability to control your pages and cater to the unique needs per your subdomain.
Formatting: On the pages tab, the first column is the URL of the page that you would like to apply the changes to. The second and third columns should be filled with the content and the content type of the URL pages. The content refers to the general structure of the page while the content type refers to the type of data that is present on the page. For example, if the page type is text/html or if it is application/json.
Find and Replace
This sheet is used to create the rules for finding and replacing objects on a webpage.
Formatting: The first column is the URL where you want to find and replace something. The second column is the key, that is the target that you want to find. The third column is the value of the key. The fourth column is the selector that determines the key. Selectors can be tags such as
p, etc. The final column takes is in a binary comment value for the validity of the key.
This JSON-LD sheet is used to specify the rules for using and creating the linked data for your webpages.
Formatting: On the JSON-LD tab, the first column is the URL of the webpage. The second column is the linked data column. This column is used to specify what the data type is. It can either be a data structure that has unique properties, or it can be a script that automates actions. It can also be a script that uses certain data structures. The third column takes in a true or false value based on if your data structure is a script or not. The final column is the comment column that checks the validity of your JSON-LD.
The response codes sheet template is used to outline the rules for using response codes for your page(s). You can use response code rules if you need to change the response code on some pages.
Formatting: The formatting specifications for Response codes is straightforward. The first column contains the URL of the webpage on which you would like to apply the relevant response code. The second column contains the response code.
Additional Information: Response code rules should change the page response code. Redirects and errors have bigger priority than response code rules. Response code rules can also be applied to html / pdf requests. Response code rules can not be applied to robots.txt and sitemap.xml requests. In addition, response codes should be visible on the Chrome extension. Response code rules could be used with wildcard links. There is no ability to use YAML rules. It is not possible to use redirect codes (300–399). This means that the ranges that you can Response Codes in are as follows:
Informational responses (
Successful responses (
Client errors (
Server errors (
To publish your SEO fixes, please see the article, “How to publish SEO solutions on RankSense.”
If you wish to use RankSense to monitor the performance of certain URLs without making an SEO change within the app, you can use the monitoring rules. Please see the article "How to use RankSense to monitor SEO changes implemented without the app."