A GeneratePress site can look finished while its page titles, navigation or search settings still need attention. The useful question is which part of the WordPress stack owns each setting, and how you can verify the result on a real page.
This guide uses SeoNative as a working example. On 19 September 2026, we checked the active theme and plugins, the public homepage and the Start Here page. The configuration observations below do not establish rankings, indexing or a performance improvement.
Quick Answer
Use GeneratePress for the page layout, WordPress for the content and URL structure, and a clearly assigned SEO plugin for metadata. Configure one layer at a time, then inspect the public output. A good setup produces readable pages and consistent signals you can verify.
The Setup We Actually Checked
| Layer | SeoNative Observation | Role in This Setup |
|---|---|---|
| Theme | seonative-child 1.0.0, with GeneratePress as parent | Header, footer, page layout and presentation |
| Theme extension | GP Premium active | Additional GeneratePress capabilities |
| Content blocks | GenerateBlocks and GenerateBlocks Pro active | Editable page components |
| SEO plugin | Rank Math active | SEO settings and generated metadata |
| Caching | LiteSpeed Cache active | Caching and optimization controls |
| Public starter page | One main heading and five section headings | A readable content outline |
An active plugin is an inventory fact. It does not tell us whether every option is configured correctly. On the starter page, we separately observed a self-referencing canonical URL and a robots meta tag containing index and follow. That page-level check is more useful than assuming an installation screen proves the output.
Start With WordPress Settings
For a public site, review Settings → Reading and its search-engine visibility option. WordPress documents that the discourage-indexing option asks search engines to exclude the site; it does not make the website private. WordPress Reading settings.
Next, review Settings → Permalinks. Choose a structure you can keep. A short descriptive post slug is easy to read, but an established URL should not be changed simply to make it look cleaner. Plan the old-to-new mapping and redirects before changing a live site’s structure. WordPress Permalink settings.
Check the homepage in a signed-out window as well. Configuration update — October 26, 2026: WordPress now reports a static front page, and the active SeoNative child theme is version 1.1.0. The public landing page differs from the content stored in the designated homepage. Check the child-theme template and cache before assuming that editing the page body will change the visible homepage. Record what your theme actually displays before changing a setting to match a tutorial screenshot.
Give Each SEO Output a Clear Owner
Write down where the page title, description, canonical and structured data are configured. On our site, Rank Math is the active SEO plugin. We still check the resulting HTML because custom templates and other extensions can also affect the output.
- Open one representative page in the editor and record its title and intended URL.
- Review that page’s SEO title and description in the plugin you use. Make the description an accurate preview of the article.
- Open the public page and inspect its document title, canonical link and robots metadata.
- If you find conflicting output, identify the component generating each value before disabling or replacing anything.
For example, our starter guide declares https://seonative.site/start-here/ as its canonical. A useful check is whether that is the page you intended to make primary. Copying the homepage URL into every page’s canonical field would communicate a very different preference.
Make the Article Template Readable
Use the post title for the main heading, then organize the body with section headings that describe the reader’s next question. Preview the complete article before adding another title block: the theme may already display one above the editor content.
Our starter page’s outline moves from WordPress essentials to technical checks, Search Console and AI search. Readers can understand that sequence without studying the design. Apply the same test to your own draft: read only its headings and ask whether the intended task is clear.
- Check a long title on a narrow screen. It should wrap without covering the byline or introduction.
- Follow a contextual link and use the browser Back button. The destination and return path should make sense.
- Inspect tables and code examples on a phone. Horizontal scrolling should remain inside the element that needs it.
- Keep callouts selective. A short answer deserves emphasis; every paragraph does not.
Use a Child Theme When the Customization Needs It
SeoNative’s custom header, footer and templates live in a child theme. That keeps those changes separate from the parent theme’s files. GeneratePress explains how child templates override parent templates and why direct edits to the parent can be lost during an update. A child theme is not mandatory for every small CSS adjustment. GeneratePress child-theme documentation.
Before activating a custom theme, keep a working copy of the prior setup and check which settings are theme-specific. After activation, visit the homepage, an article, an archive and a missing-page URL. A homepage-only preview can miss the template that readers will use most.
Check the Parts That Change After Publishing
SeoNative’s latest-guides section is designed to show published posts. A draft does not exercise that part of the homepage. Once the first posts go live, we need to check their cards, excerpts, categories and destinations together.
For your own site, make a short release checklist: the article is visible where expected, its category is useful, the excerpt fits the card, and the important links work. If a cached page still displays the old result, clear the relevant cache and compare again. Do not treat an old cached view as proof that the editor lost your work.
Common Mistake
Changing the theme, metadata plugin and cache settings together makes a problem harder to locate. Record one symptom, change the component most likely to control it, and check the same URL again.
The expected outcome is a maintainable setup with a clear owner for each output. You should be able to explain what a setting changes and show where that change appears. For the wider sequence, use our WordPress starting checklist.
Watch the Topic in Context
SEO Web Design With GeneratePress
This external GeneratePress walkthrough shows practical theme and layout choices through an SEO lens. Use it as visual context, then verify current GeneratePress settings and documentation before changing a live site.
Watch on YouTube ↗ · seosve