The Search Marketing team focuses on helping grow revenue for GitLab by increasing traffic to GitLab public websites and improving conversion paths for visitors to become MQLs (Marketing Qualified Leads). We use research and data to help improve organic discovery and make sure our offers match visitor expectations across about.gitlab.com.
The Search Marketing team focuses on growing revenue for GitLab by increasing traffic that generates new accounts for sales and our self-service workflows. To arrive at our total conversion rate we divide unqiue form submit events by unique pagevies on about.gitlab.com.
We publish our total conversion rate monthly in dataStudio.
Most people entering gitlab.com and all sub-domains start their journey on a search engine. Our team's goal is to help them discover the most relevant and accurate match for their query.
We don't engage in any dark patterns to trick people or search engine bots. We focus on improving the technical signals our site sends by limiting broken pages, adding redirects, updating metadata, removing duplicate content, and providing relevant research to teams across GitLab. The rest of this page is devoted to the processes we follow to improve overall organic discovery.
If you notice something in search and have a question about why it is happening, bring your questions to #seo-improvement. The Search Marketing team is active there and happy to investigate search issues.
When search engines crawl multiple versions of a page they see them all as duplicates, unless you set a canonical version. On about.gitlab.com we use
canonical_path to add this tag to pages. To add this to a page add
canonical_path to the frontmatter with the page path. It should look something like this
In the past we set canonicals automatically across all of about.gitlab.com, but this led to some problems when a page moved. We saw lots of issues in the handbook because a page moved, but the canonical for the content was still set as a different page. This is why we manually manage canonicals for now. As we move the monorepo project forward and split out the blog and handbook from the marketing site we may add more automated canonical management.
We should link to resources that will help our readers. Be sure to include links to blog posts, guides, and other reference material. You can also include links to company or product websites if they are relevant to your topic. These links do not need to be "nofollowed" if they are informational.
However, we should use Google's guidelines on nofollowing links when we exchange a link for a product or service. It's also a best practice to ask for a nofollow link when we sponsor and disclose our links to sponsored content.
Regular website health checks should be performed. These checks are meant to ensure that there are no issues with the website that could cause issues with traffic to the site. These are the following things to check to ensure the health of the site:
Issues to look for in each of these tools:
Manual Actionsfor any URLs that have been identified as spam or harmful content. Forward security warnings to the Abuse team and follow the DMCA complaint process with the support team.
There are times we need to keep pages out of search indexes. For example, we might duplicate most of a page to improve conversion for an ad campaign. It's relatively rare to use this, but it's an important tool that helps us increase organic reach and paid advertising efficiency.
All pages are set to
meta name="robots" content="index, follow" by default. To exclude a page from the index add
noindex: true to the frontmatter, and this will set the robots metadata to
meta name="robots" content="noindex, follow".
Occasionally we need to change URL structures of the website, and we want to make sure that people can find pages they need. We use 301 redirects to send people to the right URL when it's appropriate.
We will redirect URLs included in Google's search index. A simple test to see if a page is indexed is to search for the URL with a site modifier,
site:url, using Google.
We want to reduce the number of internal redirects, which means we need to update links across about.gitlab.com when we change URLs. When you request a redirect please indicate whether or not you were able to search across about.gitlab.com and update the links for a page you're moving.
The Digital Marketing Programs team can set up and manage all redirects for about.gitlab.com.
To redirect an outdated page, open an issue with the set up a new redirect template in the Growth Marketing project. You'll need to provide the following:
If you have any questions or concerns regarding your redirect request, ask for help in the #inbound-mktg channel on Slack.
The Digital Marketing Programs team uses these technical details for the redirect process on about.gitlab.com.