SEO for Web Apps
SEO settings help search engines understand the pages and structure of a Web app. They do not guarantee indexing or ranking. Crawlability also depends on rendering, public access, content quality, and each search engine’s policies.
Before you start
Make sure the Web app can be published successfully, and prepare:
- Public pages that search engines should be able to access
- A title, description, and social media preview for each page
- The path parameter range used by SSG dynamic pages
- Verification information from search or analytics platforms
Configure global SEO
Open Settings → SEO. Rendering mode, sitemap, robots.txt, and custom Header and Body content are global settings for the current Web app.
Republish the app after changing its SEO settings. The updates take effect in production only after publishing.
Rendering mode
- CSR renders the page in the browser and is suitable for applications that do not depend on search indexing.
- SSG generates static HTML during publishing and is suitable for relatively stable public content. SSG requires the Basic plan or above.
- SSR generates HTML on the server when a page is requested. SSR requires a Single-Tenant Server.
See Rendering Modes for a complete comparison and update behavior.
Dynamic pages with SSG
Configure a path parameter range only when the rendering mode is SSG.
If a page path contains a parameter such as /article/:slug, specify its possible values so Momen can generate the corresponding URLs and static pages during publishing. You can enter fixed values or load them from a database field. When using database values, add filters so only records intended for public access are included.
Publish the app again after adding or changing dynamic content that needs a generated page. This updates both the static pages and sitemap.
Sitemap
Enable sitemap.xml to list page URLs that search engines can discover. When using SSG, configure the path parameter range for dynamic pages, then republish the app to update the sitemap.
robots.txt
Use robots.txt to allow or disallow crawling for specific paths. Do not block pages or resources that must be indexed.
User-agent: *
Disallow: /admin/Custom header and body
Custom Header and Body provides two separate global fields. Their contents apply to every page in the current Web app after publishing.
| Field | Description |
|---|---|
| Scripts/tags in Header | Scripts or tags that need to load in the page Header, such as site-verification tags or global scripts that must load early |
| Scripts/tags in Body | Scripts or tags that need to load in the page Body |
Before adding third-party code, confirm its source and required placement. Republish the app after making changes.
Configure page SEO
Page SEO settings are available only in SSR and SSG modes.
Select a page and configure the following settings.
Search metadata
| Field | Description |
|---|---|
| Title | The page <title>, used for the browser tab and as the preferred search result title |
| Description | A summary of the page content, used as the meta description |
| Keywords | Separate multiple keywords with commas |
Social media preview
| Field | Description |
|---|---|
| Title | The title shown when the page is shared; it can use the SEO title |
| Description | The description shown when the page is shared; it can use the SEO description |
| Thumbnail | The preview image shown when the page is shared; dynamic binding only |
Canonical URL
Specify the preferred URL for duplicate or substantially similar pages so search engines know which page address to treat as canonical.
Heading tags
Add H1, H2, H3, and other heading tags to the page. Each entry contains:
| Field | Description |
|---|---|
| Type | The heading level, such as H1, H2, or H3 |
| Content | The text represented by the heading tag |
Use H1 for the primary page heading, then follow the content hierarchy without skipping heading levels.
Set image alt text
Provide accurate alt text for images that communicate content so search engines and assistive technologies can understand them. Decorative images do not need to repeat nearby text.
Upload a platform verification file
Search and analytics platforms may require a specific .txt file at the website root to verify site ownership.
Get the verification file
Download the file from the platform you want to connect. Do not change its name or contents.
Upload the file
Open Settings → Global → Upload File to Root Directory and upload the verification file.
Republish the app
Save the file and publish the Web app again so the file is deployed to the production website root.
Complete verification
Return to the third-party platform and run its verification. If verification fails, confirm that the file is reachable from the production domain by its file name.
Verification files must meet these requirements:
.txtformat only- No larger than 1 KB per file
- Up to five files per project
- A new project must be published successfully at least once before uploading a file
Publish and verify
After completing the SEO settings:
- Publish the Web app again.
- Open the production URL and check the page title, description, and social media preview.
- Check
/sitemap.xmland/robots.txt. - When using SSG, sample dynamic pages with different path parameter values.
- Complete site verification in the search or analytics platform.
If production does not show the latest settings, first confirm that publishing completed, then check the page’s rendering mode and the scope of the SEO setting.