Trusted by modern launch teams

Skip to main content
DevAssistant Docs
Browse documentation
Launch6 min read

SEO & accessibility

Prepare clear search previews, useful sharing metadata, and pages people can navigate and understand.

Where to find it

  1. Project overview
  2. Project areas
  3. SEO

In this guide

A launch checklist covering metadata, indexing, headings, images, keyboard access, and forms.

Before you start: Complete the page content and choose your intended public domain. Site defaults and page overrides are separate settings.

On this page

Set the site defaults

Open SEO from Project areas. These defaults apply where a page has no SEO override.

Set site-wide defaults, then use page settings for individual overrides.
  1. 1Site defaults. Used when a page has no override.

Set site-wide defaults, then use page settings for individual overrides.

  1. 1

    Write the default metadata

    Fill Default title and Default description with useful descriptions of the site. Check Canonical base URL, especially if the intended public address differs from the current primary domain.

  2. 2

    Choose indexing and sharing settings

    Review Noindex this site. Choose an Open Graph image or enable the dynamic image option if appropriate. Check the favicon and Apple touch icon selections.

  3. 3

    Save and publish

    Choose Save SEO settings. Publish a new release for the public website to receive these changes.

Customize individual pages

In the editor, open Pages, then the page’s settings and SEO & social. Use a specific title and description for important pages rather than repeating the site default everywhere.

Before you move on

  • Each important page has a distinct, accurate title.
  • Descriptions explain what the visitor will find.
  • The canonical address uses the intended public domain.
  • Sharing images and branding icons are available assets.
  • Indexing settings match the intended visibility.

Check content and interaction

Accessibility depends on both content and behavior. Use Style to inspect individual elements, then test the rendered page in Preview.

  1. 1

    Check headings and labels

    Select headings and inspect their heading level or Accessibility → Tag. Use headings to describe the page structure, and give buttons and form fields understandable labels.

  2. 2

    Check images and readability

    Give informative images useful alternative text. Check text contrast, font size, line length, and wrapping on smaller screens.

  3. 3

    Test with the keyboard

    In Preview, use Tab and Shift+Tab through navigation, buttons, and form fields. Confirm the focused control is visible and usable.

  4. 4

    Review motion and validation

    Check the page with reduced motion enabled. Submit an incomplete form and verify that errors explain how to correct it.

Screenshots use a local sample workspace.

Hi there, how can we help?

Help centerSearch our knowledge base of how-to articlesEmail usEmail support at support@devassistant.io