Brand & Development Guidelines
The definitive reference for building with the Sitemap.xml brand, design system, and code standards. For designers, developers, and partners.
Brand Identity
Sitemap.xml bridges the gap between complex web architecture and discoverability. Our brand is technical yet approachable, precise yet human. We represent structure, clarity, and speed.
Logo Usage
- Always use the official vector files (.svg/.png) with transparent backgrounds.
- Maintain a clear space equal to the height of the "S" around all edges.
- Do not stretch, rotate, recolor, or apply drop shadows to the logo.
- The dark variant is for light backgrounds; the light variant is for dark/colored backgrounds.
Color Palette
Our palette balances technical precision with modern energy. Click any swatch to copy the hex code.
Typography
We use Inter for UI/body text and JetBrains Mono for code, data, and technical labels. Consistency in weight and scale is critical.
Design Tokens
Spacing and layout follow a 4px base grid. Border radii use consistent scaling.
Spacing Scale
Border Radius
Small inputs/labels: 6px β’ Default cards/buttons: 12px β’ Large containers/modals: 16px
UI Components
Buttons
Inputs & States
β Validated successfully
Alerts
Code & API Standards
All integrations follow RESTful principles. Authentication uses Bearer tokens via API keys. Pagination uses cursor-based navigation.
Endpoint Conventions
// Base URL GET https://api.sitemap.io/v2/sites/{site_id}/urls POST https://api.sitemap.io/v2/index/push GET https://api.sitemap.io/v2/analytics/crawls?cursor=next_page
Naming & Structure
- Use
snake_casefor all JSON keys and database fields. - Version all API routes (
/v2/...). Never mutate v1 responses. - Return consistent error objects:
{ code, message, details? } - Idempotency keys required for all POST/PUT operations.
XML Schema Rules
Generated sitemaps must strictly follow W3C/Sitemaps.org standards. Our validator enforces these rules automatically.
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> <url> <loc>https://example.com/blog/post-1</loc> <lastmod>2025-01-15T14:30:00+00:00</lastmod> <changefreq>weekly</changefreq> <priority>0.8</priority> </url> </urlset>
<loc>is mandatory. Must be absolute URLs. Max length: 2048 characters.<lastmod>must use W3C datetime format (ISO 8601).- Split index files at 50,000 URLs or 50MB uncompressed.
- Never include non-public, duplicate, or parameter-heavy tracking URLs.
Accessibility & Usage
β Do
- Maintain WCAG 2.1 AA contrast ratios (min 4.5:1 for text)
- Use semantic HTML & ARIA labels where needed
- Ensure all interactive elements are keyboard navigable
- Provide reduced motion preferences via
prefers-reduced-motion
β Don't
- Use color alone to convey status or meaning
- Override focus outlines without providing alternatives
- Hardcode font sizes in pixels for body text
- Block crawler access via
robots.txtunless intentional
Assets & Downloads
Access official vectors, export templates, and integration kits through the partner portal.