Home›Audits›Atlassian

Public brand audit · SaaS

Atlassian SEO Audit

A 100-page technical SEO crawl of atlassian.com, conducted on October 4, 2026.

100 Pages crawled37s Crawl time23 Issue typesOct 4, 2026 Audit date

Independent SiteAuditLint analysis

SiteAuditLint crawled 100 URLs on atlassian.com and found no critical issues. The main patterns are a link to github.org, a domain that does not resolve, on 35 collection pages, 8 pages without an H1 including /software/jira, and HTML up to 5 MB on 44 pages.

MetricResult
Pages crawled100
Crawl time37s
Health score94 / 100 (Excellent)
Issue types detected23
Critical / warnings / opportunities / info0 / 63 / 363 / 14
Audit dateOctober 4, 2026

What stood out

0critical issues and no 4xx or 5xx responses
35collection pages link to https://github.org/, which could not be reached
8pages have no H1, including /software/jira and /blog
2,516 KBhomepage HTML size, with the largest page at 5,175 KB
88pages with self-referencing canonicals, and 89 with hreflang

Overall assessment

atlassian.com is in strong technical condition. No 4xx or 5xx responses were recorded, 88 of 91 analyzed pages carry self-referencing canonicals, 89 carry hreflang, and all nine AI crawlers are allowed with an llms.txt file published.

The broken link pattern comes from one URL. Collection pages link to https://github.org/, which does not resolve. The intended destination is most likely github.com.

Page weight and headings deserve attention next. 44 pages exceed 500 KB, with a median of 1,480 KB, and the Jira product page, the blog index and several contact forms have no H1.

Audit methodology

SiteAuditLint started from the website's homepage and crawled up to 100 URLs by following discoverable internal links and the URLs listed in the XML sitemap. Results represent the URLs reached during the crawl and do not constitute a complete audit of the entire website.

Starting URLhttps://atlassian.com/
Crawl limit100 URLs
URLs crawled100 (99 HTML)
Crawl dateOctober 4, 2026, 11:15 UTC
Crawl duration37s
Crawl methodHomepage start, internal link and sitemap discovery, robots.txt respected, raw HTML analysis
ToolSiteAuditLint Desktop SEO Crawler
ScopePublicly accessible URLs reached during the crawl

Technical SEO scorecard

Scores are the category scores SiteAuditLint calculates as part of its Site Health Score.

AreaScoreKey finding
Overall health94Excellent rating from SiteAuditLint
Technical96Navigation links to 301 redirects, 1 noindex whitepaper
Content972 thin sign-up pages
Performance9444 pages over 500 KB, 8 slow responses
AEO97All 9 AI crawlers allowed, llms.txt present

Major findings

1. Links to github.org

Medium

35 affected pages · SiteAuditLint severity: Warning

Finding: 35 collection pages link to https://github.org/, which failed to connect. 38 pages in total link to a broken external URL.

Why it matters: github.org is not GitHub's domain. A typo in a shared integrations block repeats on every collection page. See broken link checker.

URLBroken target
https://www.atlassian.com/collections/strategy/customershttps://github.org/ [ConnectError]
https://www.atlassian.com/collections/strategy/resourceshttps://github.org/ [ConnectError]

Recommended fix: Change the link to https://github.com/ in the collections component.

2. Missing H1 on key pages

Medium

8 affected pages · SiteAuditLint severity: Warning

Finding: 8 pages have no H1, including https://www.atlassian.com/software/jira, /blog, /get-started and three /company/contact/ forms.

Why it matters: The Jira product page is one of the highest-value pages on the site. The H1 states its topic for crawlers and screen readers.

URLEvidence
https://www.atlassian.com/software/jiraNo H1
https://www.atlassian.com/blogNo H1
https://www.atlassian.com/company/contact/general-inquiriesNo H1

Recommended fix: Add an H1 to the Jira product page and the blog and contact templates.

3. Very large HTML documents

Medium

44 affected pages · SiteAuditLint severity: Opportunity

Finding: 44 pages exceed 500 KB of HTML. The median is 1,480 KB, the homepage is 2,516 KB and the largest page is 5,175 KB.

Why it matters: Multi-megabyte HTML slows download and parsing, especially on mobile.

URLHTML size
https://www.atlassian.com/2,516 KB
https://www.atlassian.com/agile1,989 KB
https://www.atlassian.com/collections1,569 KB

Recommended fix: Review the global layout for inlined data, SVG and repeated menu markup.

4. Navigation links to redirects

Low

51 affected pages · SiteAuditLint severity: Opportunity

Finding: 51 pages link to internal URLs that 301 redirect, including /software/jira/align, /enterprise/services, /rovo and /university.

Why it matters: Links in shared navigation that pass through a redirect add a hop on every click and crawl.

Recommended fix: Update the navigation to link to final URLs.

5. Slow responses

Low

8 affected URLs · SiteAuditLint severity: Warning

Finding: 8 URLs took longer than 1,000 ms. The homepage took 1,674 ms and the slowest was 1,947 ms.

Why it matters: The homepage is the main entry point and also the second-largest document.

URLResult
https://www.atlassian.com/1,674 ms
https://www.atlassian.com/collections/software1,233 ms

Recommended fix: Reducing HTML size on the homepage is likely to help response time as well.

6. Missing structured data and Open Graph images

Low

42 pages without structured data · SiteAuditLint severity: Opportunity

Finding: 42 pages have no structured data, mostly collection pages. 31 pages lack og:image. 2 blog pages leave 30 images each without alt text.

Why it matters: Structured data and Open Graph images describe pages to search engines and social platforms.

Recommended fix: Add Product or SoftwareApplication markup and a default og:image to the collections template.

What's working well

  • No 4xx or 5xx responses across 100 URLs.
  • 88 pages carry self-referencing canonicals and 89 carry hreflang.
  • Parameterized sign-up and contact URLs canonicalize to clean versions.
  • All nine AI crawlers are allowed and an llms.txt file is published.
  • 11 pages carry FAQ markup.
  • No mixed content, missing HSTS or missing viewport tags.

Priority fixes

  1. Correct github.org to github.comOne component, 35 pages. Pages affected: 35
  2. Add an H1 to /software/jira and the blog8 pages. Pages affected: 8
  3. Reduce HTML size on the homepage and hubs44 pages. Pages affected: 44
  4. Link navigation to final URLs51 pages. Pages affected: 51
  5. Add structured data to collection pages42 pages. Pages affected: 42

Crawl data

MetricResult
URLs crawled100
HTML pages99
2xx responses91
3xx redirects9
4xx responses0
5xx responses0
Missing titles0
Missing meta descriptions4
Missing H1s8
Self-referencing canonicals88
Noindex1
Pages without structured data42
Missing og:image31
HTML over 500 KB44
Slow responses (over 1,000 ms)8
AI crawlers allowed9 of 9

On-page counts (titles, descriptions, headings, canonicals) are measured across the 91 URLs that returned an HTML page with a 200 status.

Audit limitations

Scope of this audit

The crawl was limited to 100 URLs and started from the homepage, so only URLs discovered through internal links and the XML sitemap are represented. A 100-URL crawl does not represent the entire website. Findings reflect the site at the time of the crawl on October 4, 2026. SiteAuditLint analyzed the HTML returned by the server, so content added later by JavaScript and responses that differ for automated clients may not match what a browser shows. This audit evaluates technical observations, not overall business or search performance.

This is an independent SiteAuditLint analysis of publicly accessible pages. It was not requested or endorsed by Atlassian, and it does not imply that Atlassian uses SiteAuditLint.

Audit record

Audit dateOctober 4, 2026
Crawl started11:15 UTC
Starting URLatlassian.com
URLs crawled100
Crawl duration37s
Health score94 / 100