Choose the right property
Search Console helps you see how Google discovers and presents your site. Sign in at Google Search Console with the account that should own the property. Check for an existing property before creating another one.
A Domain property covers protocols and subdomains and uses DNS verification. A URL-prefix property covers only the matching URL prefix and supports additional verification methods. For a site whose preferred address is https://example.com/, enter that exact HTTPS prefix if you choose the second route. Google's property guide explains the scope differences.
Prove ownership
For Domain verification, add the exact DNS record Google supplies at your DNS provider. Keep existing records intact, then return to verify. For a URL-prefix property, an HTML meta tag or supplied verification file may be more convenient if you control the site. Place a meta tag in the public homepage's head, not in visible page text. Use the exact value from your own account.
Follow Google's ownership verification instructions for the selected method and keep the verification record or tag in place afterward. If you cannot change DNS or site code, ask the current verified owner to grant suitable access.
Check the site before submitting it
Open the important pages without signing in. Confirm they return a successful response, show useful content, and have the intended canonical URL. A public page meant for search should not be blocked by an accidental noindex setting. Keep owner workspaces, private notes, and internal utility pages out of public discovery.
Review robots.txt and the XML sitemap. The sitemap should list canonical public URLs that work, not broken links, staging addresses, or every possible URL parameter. Wealth Experiment's public sitemap is wealthexperiment.live/sitemap.xml.
Submit and inspect
In the property's Sitemaps area, submit the sitemap address and review the result. Use URL Inspection for the homepage and a representative article. Compare Google's known information with a live test when troubleshooting. If the page is eligible, you can request indexing through the available interface.
Submission and an indexing request do not guarantee inclusion or a ranking. Google's URL Inspection documentation explains the tool's reports. Keep publishing useful work and linking related pages so discovery is not dependent on a single manual request.
Build a weekly review habit
Look for indexing errors first, then review search queries, impressions, clicks, and the pages receiving them. A new property can have little data, and reporting is not instant. Avoid rewriting a page because of a single day's movement.
When a query is relevant but the page is unclear, improve the answer and title. When impressions come from an unrelated question, consider whether the page's promise is too broad. Record the change and review later. Use analytics for what visitors do after arrival; Search Console and analytics answer different questions and their totals need not match.
Your next move
Check whether your property exists, verify the correct scope, and submit the canonical sitemap before reviewing a representative page.