Technical SEO · Supporting checklist

HTTPS SEO Checklist

An HTTPS SEO checklist is a secure-delivery audit for checking that visitors and crawlers reach the right pages through trusted encrypted connections. Verify certificates, trace HTTP redirects, fix mixed content and align preferred URLs. Use the same sample URLs to finish with a practical migration test record.

Free to useNo account neededSaved in your browser
A page redirects toward a locked destination, while image and document resource paths lead to the same destination.
Check secure destinations, redirect paths and resource URLs across your pages.
Your working checklist

Work through the checklist

Click a square to mark a task as Pass. Click again to undo. Use the result menu for a problem, a blocker or a task that does not apply. You do not need to enter notes.

15 checks

Check Secure Access and Certificate Coverage

Secure access means the intended hostname opens over HTTPS with a trusted, current certificate. Test your public entry points before changing redirects or indexing signals.

List the public hosts and URL patterns to test

Choose a sample that catches protocol and hostname gaps.

Use this for: Sites being moved to HTTPS or checked for secure-delivery regressions.

List your preferred public hostname, alternate hostnames that visitors still use and important page templates. Include the homepage, a deep service or product page, a document and a URL with meaningful parameters if your site uses them. Use an existing crawl or CMS URL list when available.

For each entry point, identify the intended final HTTPS page. Include only domains you operate or are authorized to test. This planning task can pass when the sample and expected destinations are clear; it does not certify the site as secure.

Example

Hypothetical example: A repair business tests the bare domain, its www alias, a service page and a booking landing page instead of checking only the homepage.

  1. List the public hostnames and representative URL patterns.
  2. Name the expected final HTTPS page for each.
  3. Keep the same samples for the routing and resource checks.
More help and optional notesHigh · Site owner or SEO lead
PassThe sample includes relevant entry hosts, templates and expected final destinations.
FailA public alias or important URL pattern is omitted from the test scope.

If it fails: Add the missing entry point or pattern before making site-wide conclusions.

Retest: Refresh the sample after domain, routing or template changes.

Not applicable: No URLs or implementation in this task’s scope.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check certificates on every public entry hostname

Catch certificate errors before a redirect or page can load.

Use this for: Every public HTTPS hostname in the sample, including redirect-only aliases.

Open each public hostname directly with HTTPS in an up-to-date browser. If a certificate or connection warning appears, stop and send the hostname and error to your hosting provider. Never click through the warning or disable certificate verification to make the test pass.

For a working page, open Chrome Developer Tools, then More tools → Privacy and security. In Security, inspect the certificate and origin details. Check the hostname coverage, validity period and trusted connection. An HTTPS alias needs a valid certificate even when its only purpose is to redirect elsewhere.

Example

Hypothetical example: The main site opens correctly, but the www alias produces a certificate-name warning before its redirect. The alias still needs a correct certificate.

  1. Open the HTTPS version of each entry hostname.
  2. Read the connection and certificate details without bypassing warnings.
  3. Send any hostname, trust or expiry failure to the host.
More help and optional notesHigh · Hosting administrator
PassEach tested hostname establishes a trusted HTTPS connection with a current matching certificate.
FailAny tested hostname produces a certificate, hostname or trust error.

If it fails: Have the host repair certificate coverage, validity or chain configuration.

Retest: Open every affected hostname again in a fresh browser session.

Not applicable: No URLs or implementation in this task’s scope.

Keep in mind: A valid HTTPS connection protects transport; it does not prove the business, content or all application behavior is trustworthy.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Confirm certificate renewal has an owner and a working check

Avoid a preventable expiry after a successful launch.

Use this for: All public certificates operated by the site or its hosting provider.

Ask your hosting administrator where certificates are renewed and where renewal failures are surfaced. Review the current renewal status or a recent successful renewal record for the public certificates. Identify who receives failures and who can fix them.

If renewal is automatic, confirm that it covers every public hostname and still works after DNS, CDN or hosting changes. Do not treat a dashboard’s “automatic” label as proof that renewal has succeeded. Use Blocked if the renewal process cannot yet be verified.

Example

Hypothetical example: The website has a valid certificate today, but an old employee receives renewal failures. The business assigns a current owner and checks the host’s renewal status.

  1. Find the renewal process and latest available result.
  2. Confirm the public certificates and responsible contact.
  3. Check how a failed renewal reaches that contact.
More help and optional notesMedium · Hosting administrator
PassThe renewal process covers the public certificates, with a verified recent result or safe renewal check and a current owner.
FailRenewal is failing, a certificate is omitted or nobody is responsible for failure alerts.

If it fails: Repair the renewal process or coverage and assign a current operator.

Retest: Verify the next renewal result and revisit after hosting or DNS changes.

Not applicable: No URLs or implementation in this task’s scope.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Trace HTTP Requests to the Correct HTTPS Page

A protocol redirect should lead to the equivalent secure page. Inspect the actual response chain so a browser upgrade or working homepage does not hide a broken route.

Verify an actual permanent redirect from HTTP

Confirm that the server or edge moves public page requests to HTTPS.

Use this for: Public HTTP page URLs that should permanently resolve to HTTPS.

Use a redirect-reporting crawler or ask your developer for a GET response trace of each HTTP sample. Check the returned status and Location destination. For a permanent HTTP-to-HTTPS move, a server-side 301 or 308 should point toward the intended secure page.

A browser may upgrade a request because of remembered HSTS or another HTTPS feature before contacting HTTP. A browser-internal redirect is not evidence that the server returned a redirect. Compare with a request tool that reports the actual network response, without disabling TLS checks.

Example

Hypothetical example: Typing an HTTP address ends on HTTPS, but the browser reports an internal upgrade. A separate response trace is needed to confirm the server redirect.

  1. Test each HTTP sample with a response-tracing tool.
  2. Read the actual status and redirect destination.
  3. Distinguish a server response from a browser-only upgrade.
More help and optional notesHigh · Developer or hosting administrator
PassThe actual HTTP response permanently redirects the sampled page to its intended HTTPS destination.
FailHTTP serves the duplicate page directly, uses an unintended temporary move or redirects to the wrong page.

If it fails: Have the developer correct the server or edge redirect rule for the intended permanent move.

Retest: Repeat the same GET response trace after the rule changes.

Not applicable: No URLs or implementation in this task’s scope.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Remove HTTPS downgrades, loops and avoidable extra hops

Keep the secure route direct and reliable.

Use this for: Sampled URLs with protocol or hostname redirects.

Expand every hop in the redirect trace. Confirm that the route finishes on the intended HTTPS URL without returning to HTTP, cycling between hosts or failing at an intermediate destination. Test the bare domain and www version separately if both are public entry points.

Where practical, combine hostname and protocol normalization into one permanent hop to the final page. A working extra hop is a cleanup finding, not proof that rankings are lost. Prioritize loops, downgrades and broken destinations before a harmless additional hop.

Example

Hypothetical example: The HTTP service page redirects to HTTPS www, then back to HTTP without www. The conflicting hosting rules must be reconciled.

  1. Expand the complete redirect chain.
  2. Look for downgrades, loops and incorrect intermediate hosts.
  3. Give the developer the original URL and expected final URL.
More help and optional notesHigh · Developer
PassEach tested chain ends at the correct HTTPS page without loops, downgrades or avoidable intermediate redirects.
FailA chain downgrades, loops, fails or takes an avoidable intermediate route.

If it fails: Reconcile overlapping redirect rules and point the source directly to the valid final page where possible.

Retest: Retest every entry host affected by the shared rule.

Not applicable: No URLs or implementation in this task’s scope.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Test deep paths, meaningful parameters and missing pages

Prevent a broad redirect rule from changing the visitor’s destination.

Use this for: Sites with deep routes, parameters or shared redirect rules.

Compare the requested page with the final content after the protocol redirect. Test deep paths and parameters that change content or functionality, such as a product variant or language choice. Preserve the information the destination needs; tracking-only parameters can follow your site’s agreed policy.

Include a deliberately nonexistent path. Its HTTPS destination should retain an appropriate not-found response rather than silently display the homepage with a success code. Do not send every old URL to the homepage simply because the protocol changed.

Example

Hypothetical example: An HTTP booking page with a selected service lands on a generic homepage after migration. The rule preserved HTTPS but lost the useful destination.

  1. Test a deep path and any meaningful query variation.
  2. Compare the final content and selected state with the request.
  3. Test a nonexistent path and its final response.
More help and optional notesHigh · Developer
PassValid requests retain the intended content or state, and missing routes remain honest not-found responses.
FailThe redirect loses important path/query information or turns unrelated missing pages into the homepage.

If it fails: Correct the mapping and preserve meaningful route data; retain appropriate missing-page handling.

Retest: Repeat the same valid and missing examples after repair.

Not applicable: No URLs or implementation in this task’s scope.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check that intended search pages are accessible on HTTPS

Catch migration blocks on the final secure destination.

Use this for: HTTPS pages intended for public search.

Open the final HTTPS page directly. Check the main document status, visible content and any login or challenge barrier. For a page intended for public search, review its robots.txt access and page-level indexing directives with your SEO or developer.

When Search Console access is available, run URL Inspection’s live test for a sample destination. Keep intentional restrictions on private or non-search pages. A successful live fetch establishes current access; it does not establish that Google has indexed the page.

Example

Hypothetical example: A service page works over HTTPS but still carries the launch-stage noindex directive. The owner removes that accidental directive only when the page is approved for search.

  1. Open the final HTTPS destination directly.
  2. Check its response, public content and intended indexing rules.
  3. Use an available live inspection to investigate access failures.
More help and optional notesHigh · SEO lead and developer
PassThe final page returns the expected successful content and has no unintended crawl or indexing barrier.
FailAn error, login barrier or unintended directive prevents access to the intended public page.

If it fails: Repair the specific access or directive problem while retaining intentional privacy controls.

Retest: Retest the direct URL and relevant live inspection after repair.

Not applicable: No URLs or implementation in this task’s scope.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Align Links and Search Signals With HTTPS

Preferred page addresses should agree across the page, navigation and discovery files. Fix the source of an old HTTP reference so it does not return at the next publish.

Check that canonicals name the intended HTTPS URLs

Avoid a conflicting preferred-address signal.

Use this for: Indexable HTTPS pages and any duplicates with canonical declarations.

For each sampled page, use View page source or your crawler’s canonical report to find rel="canonical". Compare the full URL with the intended HTTPS destination and test that destination directly. Check the rendered head as well if JavaScript changes metadata.

A page that is the preferred version normally names its own HTTPS address. An intentionally consolidated duplicate can name another appropriate HTTPS canonical. Check for competing declarations in HTML or response headers rather than forcing every URL to self-canonicalize.

Example

Hypothetical example: A secure service page still declares its old HTTP address as canonical because the CMS base URL was not updated.

  1. Find the declared canonical in the page or crawl report.
  2. Compare it with the intended preferred HTTPS URL.
  3. Check for conflicting HTML, header or rendered declarations.
More help and optional notesHigh · SEO lead and developer
PassThe canonical consistently names the correct accessible preferred HTTPS page.
FailA declaration points to HTTP, an incorrect page or a conflicting destination.

If it fails: Update the responsible template or CMS setting and reconcile competing declarations.

Retest: Recrawl the affected templates and compare source and rendered canonicals.

Not applicable: No URLs or implementation in this task’s scope.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Update sitemap and language references to the secure destinations

Keep discovery annotations consistent with the protocol move.

Use this for: Sites with a sitemap or language-version annotations.

Open the current XML sitemap or sitemap report and inspect page addresses. It should list the intended absolute HTTPS canonical URLs rather than stale HTTP entries or redirecting alternatives. Check the sitemap generator’s base URL if old entries return after regeneration.

If the site uses hreflang, compare the language-version addresses and their return references after the move. Keep the original language relationships intact while changing the protocol. Mark the language part Not applicable in your own working record when no language annotations exist.

Example

Hypothetical example: The English page moved to HTTPS, but its language annotation still points to the old French HTTP URL. Both pages’ annotations need the correct secure pair.

  1. Check sitemap page addresses against the final HTTPS URLs.
  2. Inspect language annotations when used.
  3. Repair their generating settings and validate the regenerated output.
More help and optional notesMedium · SEO lead and developer
PassSitemap entries and applicable language references use the correct final HTTPS URLs.
FailDiscovery annotations still name stale HTTP or unintended redirecting addresses.

If it fails: Update the sitemap or language annotation source, preserving the correct page and language mapping.

Retest: Regenerate the files and recheck the affected URLs and return annotations.

Not applicable: No sitemap or language annotations exist in the audited scope.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Find Insecure Resources and Broken Secure Replacements

An HTTPS document can still request insecure images, scripts, fonts or embeds. Use the browser’s request information to find the originating reference and verify its replacement.

Find mixed-content requests on representative templates

Identify insecure subresources that a normal visual check can miss.

Use this for: HTTPS pages that load images, scripts, styles, media or embeds.

With Developer Tools open, reload a representative HTTPS page and inspect Console warnings and the Privacy and security panel. Open non-secure origins in the Network panel where available. Check scripts, styles, images, fonts, media and embedded widgets, including content loaded after scrolling.

Mixed content means the secure page requests a resource through HTTP. Some requests are blocked and others may be upgraded automatically. A page that appears complete can therefore still contain stale insecure references. Keep the originating page and resource together when passing the finding to the developer.

Example

Hypothetical example: A service page’s main text works, but an old booking script is blocked as mixed content. The missing booking widget is traced to that exact request.

  1. Reload with Console and security information available.
  2. Find blocked, insecure or automatically upgraded resource requests.
  3. Identify which template or content field created each relevant request.
More help and optional notesHigh · Developer
PassThe sampled page states contain no unresolved mixed-content requests or warnings.
FailA template requests an insecure resource, even if the browser upgrades it.

If it fails: Replace the insecure reference with a tested secure source or remove the dependency when appropriate.

Retest: Reload affected page states and repeat the Console and Network check.

Not applicable: No URLs or implementation in this task’s scope.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Verify secure assets actually load and keep the page useful

Do not replace HTTP text without checking the resource behind it.

Use this for: Resources identified as insecure or broken during the HTTPS audit.

Open the proposed HTTPS asset or inspect its request in Network. Confirm it succeeds with the expected file type and content. Then update its source in the CMS, stylesheet, template or third-party integration that emitted the old address.

If the provider does not support HTTPS, use an authorized secure replacement or remove the dependency. Test the repaired page’s layout and useful features. Do not switch the page back to HTTP, allow insecure content or weaken browser security to keep an old widget running.

Example

Hypothetical example: Changing an old image address to HTTPS returns an HTML error page. The editor uploads the authorized image to a working secure media location instead.

  1. Test the proposed HTTPS resource before replacing it.
  2. Update the actual source reference.
  3. Confirm the page and required feature still work.
More help and optional notesHigh · Developer or site editor
PassThe replacement loads securely as the expected resource and the affected page remains usable.
FailThe new URL fails, returns the wrong resource or leaves the feature broken.

If it fails: Choose a supported secure resource or remove the dependency, then repair its references.

Retest: Reload representative pages with a fresh request and inspect the resource response.

Not applicable: No insecure or broken resource needs replacement.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check secure destinations for forms and embedded services

Keep the next step secure after the public page loads.

Use this for: Pages with forms, booking widgets, checkouts or third-party embeds.

Inspect contact, booking, checkout and other relevant entry points without sending personal information. Check a form’s action destination and an iframe’s source in Developer Tools, or ask the developer to show the configured endpoint. Confirm the intended service uses a valid HTTPS address.

For JavaScript submissions, ask the developer to verify the actual destination in an approved test environment using synthetic data. A secure page shell does not establish where its form sends information. Keep private services and authentication controls intact.

Example

Hypothetical example: The contact page is HTTPS but a legacy form action still uses HTTP. The developer replaces the endpoint and verifies it safely with synthetic test data.

  1. Inspect the form or embed’s configured destination.
  2. Confirm the intended endpoint supports valid HTTPS.
  3. Use an approved synthetic test if the destination is generated by JavaScript.
More help and optional notesHigh · Developer
PassRelevant destinations and tested requests stay on valid HTTPS and preserve the intended function.
FailA form, embed or generated request uses HTTP or fails on its secure replacement.

If it fails: Update the integration to a supported secure endpoint and retest its function safely.

Retest: Repeat endpoint inspection and an authorized synthetic test after the change.

Not applicable: No forms, embedded services or relevant generated requests are present.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Review HSTS Safely and Retest the Migration

HSTS is a security policy with operational consequences. Review it with the person who manages your domains, then verify the original HTTPS findings on the live site.

Review HSTS scope before enabling or expanding it

Avoid locking legitimate hosts into an unsupported HTTPS policy.

Use this for: Sites already using HSTS or considering an HSTS policy change.

Ask the hosting administrator whether Strict-Transport-Security is already sent on HTTPS responses and which hosts it covers. Review the remembered policy duration, includeSubDomains scope and any preload status. HSTS tells browsers to use HTTPS on future visits.

Before enabling or expanding it, the administrator should verify reliable HTTPS and renewal across the affected hosts, including legacy subdomains. Preloading requires a separate readiness decision because removal is not immediate. Do not copy a long-duration preload configuration just to clear an SEO warning.

Example

Hypothetical example: A business’s main site supports HTTPS, but an old public subdomain does not. The administrator resolves that dependency before considering a policy covering all subdomains.

  1. Identify the current HSTS header and affected host scope.
  2. Review HTTPS and renewal readiness with the administrator.
  3. Approve any change through the normal security change process.
More help and optional notesMedium · Hosting or security administrator
PassThe policy’s scope and readiness are verified, with no known incompatible covered host; any proposed expansion has a safe operational plan.
FailThe active policy covers an incompatible host, or a proposed change ignores subdomain and renewal readiness.

If it fails: Have the administrator repair affected hosts or revise the planned policy safely.

Retest: Recheck headers and representative covered hosts after an approved change.

Not applicable: No HSTS policy is used and no policy change is being evaluated.

Keep in mind: This is a policy-readiness review, not a requirement to enable HSTS or preloading to pass a general SEO audit.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Retest the original URLs and review later search signals

Close HTTPS findings only after their observed behavior is corrected.

Use this for: Completed HTTPS fixes or a protocol migration.

Repeat the same certificate, redirect, final-page, canonical and resource checks for the original failing samples. Include another page using the same repaired template or host rule. Keep the response trace or your existing issue record if useful; notes in this checklist are optional.

For a protocol migration, compare later Search Console indexed-page information and selected canonicals with the intended HTTPS pages. Treat delayed indexing separately from a live defect. Keep working HTTP redirects for old links; do not remove them just because one sample has moved in search.

Example

Hypothetical example: A repaired redirect works on the homepage but still fails on service paths. The issue stays open until the affected pattern passes the same test.

  1. Repeat each original failing check on the live change.
  2. Check another page affected by the shared fix.
  3. Review later indexed information without treating it as a live-test result.
More help and optional notesHigh · SEO lead and developer
PassThe repaired behaviors pass the repeated checks, and any separate indexing uncertainty is clearly distinguished.
FailAn original defect persists or the shared repair breaks another sampled route.

If it fails: Repair the remaining route, signal or resource problem before closing that finding.

Retest: Revisit the sample after relevant hosting, CDN, certificate or template changes.

Not applicable: No HTTPS fix or migration has been made yet.

Optional: the affected page or template, what you observed and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Reset this checklist?

This removes saved statuses, evidence and result dates for the checks on this page. Other checklists keep their records. Export a CSV first if you need a copy.

A useful result, every time

Check a task. Choose a result.

This is a manual SEO workflow. It helps you decide what to investigate and keep a usable record. It does not crawl your website or verify your answers automatically.

  1. Choose your scope. Pick the relevant task group and representative pages you are authorized to inspect.
  2. Run the stated check. Follow the steps, then choose your result. Click the square for Pass, or use the result menu for another status. You do not need to type anything.
  3. Assign the next action. Fix a problem when you can, or ask the right person for help. Optional notes can remind you what to do next. Check the result again after a fix.

What your progress means

Review progress counts passes and failures against applicable checks. Failed work still counts as reviewed. Blocked and untested checks remain unfinished. This is not an SEO score.

Untested
You have not checked this yet.
Pass
You checked it and it works as described.
Fail
You checked it and found something to fix.
Blocked
You need access, information or someone’s help.
Not applicable
This task does not apply to your website.

Export CSV downloads the checks currently shown and any optional notes. Print expands the instructions for that view. Saved results stay in this browser; there is no account sync.

Apply the workflow

What Should You Do With the HTTPS Audit Results?

Turn each failed connection, route, signal or resource into a specific repair and repeat the same check after the change.

What Should an HTTPS Migration Test Record Include?

An HTTPS migration test record connects the original address to its final response, certificate, canonical and resource outcome. Keep one row for each important entry point so a working final page does not conceal an earlier failure.

Use the hypothetical rows below in your own spreadsheet or issue tracker. Add the test date and tool if helpful. Export CSV on this checklist saves your checklist view and optional notes; it does not crawl the site or build the response trace for you.

Hypothetical HTTPS checks and the repair each result requires.
Entry pointObserved resultDecisionRetest
HTTP service page.Permanent redirect to the matching HTTPS page; secure assets load.Keep the route; check the other shared templates.Repeat after routing changes.
HTTPS www alias.Certificate warning appears before the redirect.Repair certificate coverage for the alias.Open the alias without bypassing the warning.
HTTPS contact page.Page works but the form destination uses HTTP.Replace and safely test the form endpoint.Inspect the destination and approved synthetic request.
HTTPS article.Canonical still names the HTTP version.Correct the canonical’s generating setting.Compare source and rendered head again.

Which HTTPS Issues Should You Fix First?

Fix HTTPS issues that block safe access first: certificate errors, redirect loops, broken destinations and blocked essential resources. Then correct conflicting canonicals and discovery references, followed by avoidable HTTP detours in your own links.

Group related findings by their actual cause. A single shared widget can affect many pages, while a certificate failure on one entry hostname can stop visitors before any page loads. Mark unresolved checks Blocked when you need hosting access or specialist help rather than recording a pass.

Does Seeing HTTPS in the Address Bar Prove the Migration Works?

Seeing HTTPS in the address bar proves only part of the migration. It does not verify every entry hostname, the server’s HTTP redirect, canonical declarations or requests made by embedded resources.

Browsers can upgrade an HTTP request before it reaches the server. Use an actual response trace alongside the browser check, and test a deep page and the features your visitors rely on.

Do You Need Search Console’s Change of Address for HTTP to HTTPS?

You do not need Search Console’s Change of Address tool for a protocol-only HTTP-to-HTTPS move. Confirm that your accessible Search Console property includes the HTTPS URLs, then use the appropriate sitemap, indexing and URL Inspection information.

A live test describes current availability. The indexed result describes Google’s recorded version and may be older. Neither a sitemap submission nor a valid HTTPS page guarantees indexing or rankings.

Which Checklist Should You Use After the HTTPS Checks?

Use the next checklist for the remaining problem, while keeping the HTTPS samples for a final regression test.

A clear process, with honest limits.

Follow the steps, choose the result that matches what you found, and check again after changes. Notes are optional. A completed check does not guarantee indexing, traffic or rankings. How the checklists work.