This is one of the advanced features available to sites that are managed by an agency. If you need a recommendation for an agency that uses RankSense, please contact us!
RankSense has the ability to make the following types of SEO changes:
- Canonical tags
- Meta robots tags (index, follow, noindex, nofollow)
- Meta titles
- Meta descriptions
- Hreflang tags
- 301 redirects
- 404 error fixes (these are also 301 redirects, but we distinguish the two)
- Media alternate tags (used when there is a separate mobile site)
Important: RankSense will overwrite the robots.txt, HTML code, 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. You can see a template sheet here:
Rules sheet template
You can make a copy of this sheet to fill in with your own SEO rules. The sheet does contain examples, so be sure to delete unwanted rules before publishing.
Each tab on the template controls a different type of SEO change listed above. For every tab except robots.txt, the URL that you want to change goes in the first column. The second column is typically the desired change, but in some cases, a third column is needed. The last column is an optional comment. I’ll explain the details of each tab below.
We allow wildcards in the rules, which can considerably reduce the number of rules you need to publish in certain circumstances. I’ll explain the wildcards at the end of this article.
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.”
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.
This tab 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.
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.
This tab 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).
This tab 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 tab is used to add or overwrite meta titles. It does not affect the on-page content.
Formatting: Place the URL in the first column, and the desired meta title in the second column.
This tab 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 tab 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).
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, “sp” 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 tab adds 301 redirects to URLs that are currently 404 status. If the URL becomes 200 status again, the error rule will be deactivated.
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 tab adds 301 redirects, and is intended to be used for URLs that are currently 200 status.
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 tab adds alternate media tags for sites that have a separate mobile site, i.e. . Please note that the mobile site will need to be set up separately and handled with a separate rules sheet from the desktop site.
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.
All rule types that have a URL column support wildcards in that column. However, the other columns do not support wildcards.
For example, you may need to apply the same canonical URL to all pages of the type:
(That is, all URLs that begin in that way, and may contain anything else after the equal sign)
The app will allow you to enter this URL in the first column. However, you will have to specify the same canonical URL for all of these in the second column, for example:
If you want all paginated pages to be canonical to the view-all page.
The app will not allow you to use a wildcard in the second column, so you would not be able to specify that each paginated page is canonical to itself with a single wildcard rule. In that case, you would need to create separate rules for every paginated page.
To publish your SEO fixes, please see the article, “How to publish SEO solutions on RankSense.”