GitLab

Connecting a GitLab project records each production deploy as a deploy in RankDebug, with the SEO-relevant files it changed, without any change to your pipeline.

Create the token

1. In GitLab, open Preferences → Access Tokens.
2. Click Add New Token and give it a name and an expiry date.
3. Select only the read_api scope.
4. Create the token and copy it.

RankDebug refuses a token that carries any scope that can write. It keeps upstream access read-only rather than trusting a broader token to be used carefully.

Connecting

1. On Connections, click Connect GitLab and paste the token.
2. Choose the project that deploys this website. The list shows the projects on GitLab.com you are a member of.

What is recorded

RankDebug reads the project's successful deployments to an environment whose name starts with "prod". Each one becomes a deploy. If the project has no such deployments, each commit on the default branch that touched SEO-relevant files stands in for a release instead.

For every deploy, the changed files are read to find SEO-relevant changes, the same way as for GitHub. Only file paths and signal names are kept, never a line of code.

The project syncs every hour and the first pull reaches back 90 days. A deploy older than six hours when it is found is recorded, but the site is not checked for it.