Help Baidu and Google Discover a New Website: A Practical SEO Checklist

Submit a website to Baidu: start with ownership, not a ranking promise

If you are looking for “submit site to Baidu” or “baidu-site-verification”, the first job is to register the correct site and prove control of it. The next job is to provide discoverable URLs. Neither action guarantees indexing. Google Search Console is a separate registration and monitoring workflow; verifying with one engine does not verify with the other.

Official public documentation checked on 9 October 2026. Baidu's authenticated screens and your account's submission permissions were not tested for this guide. Follow the options actually offered in your account; an old screenshot is not proof that a feature is available today.

Prepare the correct address and access

Write down your final public address, for example https://www.example.com/, and a real article URL. Check these in a private browsing window. Keep HTTP/HTTPS and www/non-www consistent with the live site. Have access to the site's publishing settings or DNS provider, and use an account the site owner can retain.

Keep the existing content-first checklist: useful original pages, descriptive titles, readable mobile layout, normal internal links, accurate canonical URLs and no accidental noindex. A submission form cannot repair an empty site, inaccessible content or competing duplicate URLs. Do not remove private-area crawl restrictions to pass a verification check.

Add the site in Baidu Search Resource Platform

1. Open Baidu's official site management and sign in. Complete account requirements if prompted; this guide cannot predict your account's eligibility.
2. Find site management, then the add-site action. Baidu's own verification guide describes selecting the protocol, entering the main hostname and choosing site attributes. Choose your actual HTTPS address, not an obsolete HTTP variant.
3. Select an available ownership method. Copy the current account's instructions exactly; never reuse another site's example token.
4. Publish the verification change or save the specified DNS record. Check the public result before pressing the verification button.
5. Confirm that the correct site is listed as verified. Keep a dated record of the method and outcome. Avoid removing the proof later without checking platform requirements.

Choose and troubleshoot Baidu verification

File verification: download the issued file and expose it at the exact public URL shown by Baidu. Preserve its name and contents. An application returning its home page for every path can produce HTTP 200 without serving the verification file. Open the exact address and inspect the body, not just the status.

HTML tag verification: where offered, place the issued baidu-site-verification tag in the homepage's HTML head. Preserve existing verification tags. Publish the change and inspect the public page source. A tag pasted into article text, displayed as escaped text, or present only in an unpublished preview is not the intended proof.

DNS verification: if the platform offers it, add the exact record type, name and value it supplies. Baidu's published guide describes CNAME verification; this is not Google's Domain-property instruction. DNS panels differ in whether they append the zone name. Check the resulting full hostname and do not overwrite a record used by the live website.

If verification fails, record the message and check the chosen host/protocol, token, public file or head tag, publishing completion, login barriers and security challenges. For DNS, check the authoritative record as well as cached answers. Do not disable HTTPS or the firewall as a generic fix. Propagation and platform checks have no guaranteed completion time in this guide.

Submit URLs to Baidu when the tool is available

Open ordinary inclusion for the verified site. Use only the submission methods and quotas displayed for that site. The official VIP tools page documents differing Sitemap access; verification alone does not prove that every account has a Sitemap tab.

If Sitemap submission is offered, publish a valid public sitemap, enter its full URL in that tool and retain the result. If it is not offered, check the permitted link-submission options or official support. Do not invent an endpoint, copy another account's API token or buy a promised indexing result. API automation is not required to complete this beginner workflow.

Baidu explicitly distinguishes receiving submitted links from including their content in search. A successful submission is a recorded handoff, not proof of indexing. Use the available index, crawl and traffic reports for follow-up.

Add and verify Google Search Console separately

Use Google's property guide to choose the scope before collecting data. A Domain property such as example.com includes protocols and subdomains and uses DNS verification. A URL-prefix property such as https://www.example.com/ covers that prefix; inspect the verification methods offered for it.

For a Domain property, follow the issued DNS instructions. For a URL-prefix property, file or HTML-tag verification can be practical if you control deployment. Google's ownership guide describes the exact requirements. Keep the proof available after verification; distinguish access granted by an existing owner from independently proving ownership.

Prepare a sitemap and submit it to Google

Prefer your CMS's existing sitemap over hand-maintaining a competing one. Check that it contains final public canonical URLs, not admin, preview or redirect-only pages. Google's sitemap specification covers accepted formats, absolute URLs and file limits. Use accurate significant-update dates where lastmod is supplied; do not change every date merely to look fresh.

In the correct property, open the Sitemaps report, provide the sitemap location as the form requests, and submit. This tells Google where the file is hosted; it does not upload the file to Google. Check processing status, last read and reported errors. “Success” concerns the sitemap, not automatic inclusion of every listed URL. The report requires owner permissions for submission.

For a public site, a sitemap declaration can also appear in the existing robots file:

Sitemap: https://www.example.com/sitemap.xml

This is an example address, not a replacement robots file. Preserve existing access rules. Open the actual sitemap in a private window and inspect its XML, not a login screen or branded HTML error page.

Confirm results and handle common submission failures

• Wrong property: check whether the address falls inside the selected URL prefix. Do not diagnose HTTPS/www mismatch as a generic DNS outage.
• Verification file or tag missing: inspect the exact public file or homepage source after publishing; a preview is not enough.
• Sitemap cannot be fetched: check the report's specific error, public GET response, TLS, redirects, login requirements and security filtering. A successful HEAD request alone does not prove the XML body is valid.
• Sitemap processed but article absent: use URL Inspection on the exact article. Separate indexed information from the live test; a successful live test does not establish that Google indexed it.
• Request submitted but no ranking: Google's recrawl guidance does not guarantee inclusion. Repeated requests for the same URL do not speed crawling.

The four checkpoints are different: submission records a request; discovery means the engine knows a URL; crawling fetches its content; indexing decides whether and how to retain it for search. Ranking and visits come after these and are not promised by verification or Sitemap submission.

Keep a completion record instead of refreshing every day

Save the exact property/site, verification outcome, sitemap address and result, and inspection result for a few important pages. Then record dated impressions, clicks, queries and technical errors separately for each engine. Review technical status after a week and search performance over longer windows. Small samples and site: spot checks cannot establish a growth trend or a complete index count.

The useful routine remains: publish something genuinely helpful, link it from a relevant page, document the submission, and improve missing explanations using real queries and reader problems. If Baidu access is unavailable, record that limitation rather than marking both engines complete. This guide provides a verifiable workflow, not an account-level submission result or a traffic guarantee.