After changing the theme, the SEO fields were still filled in in the editor, but the description and canonical disappeared from the published page. In this situation, it is too early to re-enter the text in every post: the problem may be with how the theme builds the HTML document.
These instructions primarily apply to classic and custom PHP themes in WordPress. Block themes use a different template structure; you should not copy header.php into them from a random guide. First determine which type of theme is in use and which pages are missing the tags.
Description is a page description for search engines; canonical indicates its primary URL. They are located in the document's head section, so their disappearance may go unnoticed when viewing the page normally.
How to distinguish lost data from a rendering error
Choose a page with a known, manually entered description and canonical. Open the post in the editor and save the current values from the SEO plugin. Then, while logged out of WordPress, open the public page's HTML source and look for the corresponding tags.
If the data is in the editor but missing from the HTML, this is a rendering error or behavior. If the data is missing too, investigate the database migration, import, or plugin change. A change to the visual theme alone does not explain why fields were lost. You need to establish a connection between the change and the specific source of the value.
Check several templates: the homepage, a standard page, a blog post, and a product. If the problem occurs only on a service page with its own template, comparing it with a working post will quickly narrow down the search. If the tags are missing everywhere, check the shared header, active SEO plugin, and shared HTML cache.
Why classic themes need wp_head
The wp_head() function runs the hook of the same name, through which WordPress core and plugins output data in the document head. In a classic theme, it is usually called before the closing head tag. The call itself does not set the description or canonical; it lets the registered callbacks do their work.
The developer should check the header file actually used by the problematic template and how that file is included. In a custom theme, it is not always the standard header.php. Sometimes a separate landing page builds the document manually and bypasses the shared header, so regular posts work but the service page does not.
The minimal snippet below shows where the call goes; it is not a complete theme. Adding it requires checking the active template: a duplicate call can also create duplicates.
<head>
<meta charset="<?php bloginfo('charset'); ?>">
<?php wp_head(); ?>
</head>The relationship between the function and callbacks is described in the WordPress reference for the wp_head hook. If the call is already present, move on to checking the callbacks and the conditions under which they run rather than inserting a second one.
A training example with a separate service template
Imagine a site where standard pages use a shared header, but the service /services/cleaning/ has a dedicated landing page. This is an illustrative example. The service's description is saved in the SEO plugin, but the new header manually outputs only charset and title. It does not call wp_head.
The developer restores the standard shared-header include or adds the necessary call to the custom template. Then they check the entire document: the description appears, there is only one canonical, and the title is not duplicated. A single new line can fix the missing output and also reveal manual duplication that was previously hidden.
The second test URL is a regular article. Its output should remain correct because changing the shared header affects other pages. Checking only the landing page is not enough: the task concerns the template, not just one URL.
Other causes to check
Make sure the SEO plugin is active and its output has not been disabled by custom theme code or an extension. Check whether the theme adds its own robots and canonical tags. Two sources can output conflicting rules even when each looks correct on its own.
An outdated public response is covered in detail in the guide to checking the HTML cache. If the plugin itself was recently changed, also check the Yoast to Rank Math migration.
Compare the response for a regular visitor with the response for an administrator. If the data differs, find out how the page cache and CDN work. Clearing the relevant cache helps you check the new version of the HTML, but does not prove that the template has been fixed. Do not clear all caches every time before identifying which layer is serving the outdated document.
Also check whether the title remains only because it was added manually to the header. Its presence does not confirm that wp_head is working. You need to verify the actual tags expected from the plugin and make sure there are no extra copies. The editor settings and the published document must be connected by a verified result.
If the source HTML contains the correct canonical but the browser DOM shows a different one, look for a client-side change after loading. In that case, the cause is no longer limited to the PHP header. Save both versions with their URLs and timestamps so the developer can reproduce the discrepancy.
What to send the developer
In the task description, specify the theme and its version, the type of problematic template, and two test URLs: one broken and one working. Include the values from the editor and a snippet of the source HTML. “SEO disappeared” is less useful than “The description field is filled in on the service page, but meta description is missing from the public response.”
Expected result: the theme outputs data from the installed SEO plugin using its standard mechanism, without a second, independent tag system. If the implementer needs a separate title for the landing page, they should explain where it comes from and how it interacts with the plugin, rather than simply inserting a line on top of the existing mechanism.
Test the fix on a copy of the site first. For a child theme, confirm which file is being changed and why an update to the parent theme will not overwrite the change. For a block theme, ask for a solution that fits its structure. There is no universal file for all themes.
How to check a theme update after the change
Record the name of the changed file and explain how it is included. On a copy of the site, perform the planned parent theme update and recheck the service page. If the fix disappears, change how it is stored before the next routine update. This is a separate check of the solution's durability: correct HTML immediately after a manual change does not show that the change will survive routine WordPress maintenance.
How to accept the fix after release
Reopen the test pages while logged out. For each one, check the title, description, canonical, and robots in the source HTML. Record the specific values, not just whether the tags are present. A canonical pointing to the homepage for a service page is still wrong, even if the tag has appeared.
Check the page's rendering and main actions: the header, menu, form, and links. Restoring the hook may add more than SEO data, so visual and functional checks are also part of the task. Then repeat the sample check on neighboring templates.
For a general review of published pages, you can use the technical site audit; further analyses are collected in the blog. The work is complete when the editor fields appear correctly in the public document, templates do not create duplicates, and the site's main actions continue to work. Google and Yandex indexing status is checked separately afterward: it does not update just because a PHP file was saved.