An SEO plugin can expose hundreds of settings, but most sites benefit from getting a small group of fundamentals right. Start with how pages are discovered, indexed, and presented. Advanced modules should follow a real requirement, not a desire to fill every dashboard indicator.
Decide what search engines should index
List the public content types and archives that provide unique value. Posts, pages, products, and selected taxonomies may belong in search. Thin tag archives, internal search results, account pages, cart screens, and duplicate templates often do not.
Use noindex deliberately and verify the actual page output. Blocking a URL in robots rules is not the same as asking search engines not to index it.
Create sensible title templates
Set readable defaults for each content type, then allow important landing pages to override them. Keep titles descriptive and distinct. Meta descriptions do not guarantee a particular search snippet, but clear summaries help editors communicate the page’s value.
Confirm canonical URLs
Canonical tags should point to the preferred version of a page. Pay attention to filtered product lists, tracking parameters, pagination, translated pages, and content available through several paths. Do not automatically canonicalize genuinely different pages to one URL.
Review the XML sitemap
The sitemap should include canonical, indexable URLs that you want discovered. Remove test content, utility pages, empty archives, and post types that are not public. Submit the sitemap through relevant search engine webmaster tools and monitor processing errors.
Set social sharing defaults
Configure a default image and verify Open Graph and other social metadata on representative pages. Featured images should have useful crops and sufficient resolution. Preview a few links in the platforms important to the business.
Avoid overlapping ownership
Only one system should control core SEO metadata, canonicals, and sitemaps. Disable duplicate features in themes, optimization suites, or older plugins. After migration, compare source output and redirects before removing the previous tool.
Measure outcomes, not scores
Plugin checklists can catch missing fields, but they cannot decide whether content deserves to rank. Monitor crawl issues, impressions, useful queries, conversions, and the quality of indexed pages. A clean configuration creates reliable technical signals; helpful content and a coherent site structure do the rest.