Exporting Your Site, Uploading Your Site to an Amazon S3 Bucket, Validating Your Site, Using an S3 URL, with Google and then, Indexing Your Site.
I’ve included bonus information so you should go though it completely (and take notes) at least one time!
View The Process Video (Updated 05/24/2021)
Update on making bucket public (03/13/2024
Note 1:. The validation file that Google has you download to upload to your site or S3 container must not be modified or changed in any way. If the file name, it’s contents, or the location of the file, is changed in any way, the validation will fail…every time.
The content of the google validation file contains the original name the Google Verification file must have so, you can verify that the name is correct by using a text editor to look inside to check. (an html file is a text file).
Just follow these procedure and don’t change the name of the file in any way. The container will be verified. The verification file is linked to your Google account and to each URL verified – Also, never remove the verification file unless you’re deleting everything in the container and will be verifying a new container, even if you’re using the same name.
The link to get started: https://search.google.com/search-console/welcome
If verification fails it’s because Google could not find the verification file where you said it was and/or the name of the verification file was changed.
Further Clarification
Each property must be validated individually before adding any additional properties. There is no bulk validation of properties available.
The request for the validation of any property must be done, one at a time, and each request will be provided with it’s own validation file for downloading.
The validation file may be exactly the same for each property, but until Google provides the file for downloading, the property will not be linked to the validation file, making it invalid.
Validation of a property is virtually instantaneous however, that file has got to be at the exact address you provided to Google, any place else, the validation will fail immediately. You must not change, in any way, the name of the file or it’s location. This was stressed in the instructions above.
The time it takes to index a site depends entirely on Google. Indexing is usually done within a few hours and may take up to 24 hours. If you are waiting longer for indexing, Look in your GSC dashboard, select the property, and review the errors. Do not request indexing until all errors have been corrected.
You never need to request the indexing of a domain or subdomain as Google does this automatically, many times a day.
In fact, until your site has been completed, You should turn on Noindex, Nofollow for every page of your website. Remember to turn this off, for each page, when you’re ready for Google to index.
If your site has not been indexed (easily verified by entering the word site: followed directly by your complete S3 URL or your domain name do not include https:// : Examples: site: yourdomain.com or site: completeS3URL into your browser) you should check for any messages in your GSC (we cannot see your GSC dashboard). Please be patient and don’t request indexing more than once before you have resolved any issues.
Important note: Until you have successfully indexed a site and have your 5 minimum keywords ranking on the first page, do not request indexing for any other sites. The sites must be each successfully indexed before you request indexing for another site.
You must inspect your complete Amazon S3 URL, including /index.html and then Test the URL before requesting indexing – Not including /index.html to the path for your Amazon S3 URL will give you a 403 error.
Still having difficulties? Don’t be frustrated. Create a free video showing us the steps you’ve taken. This will allow us to quickly, and accurately diagnose the issue.
We recommend that you install the free Chrome extension Loom (There is also a free desktop version for more flexibility). This extension allows you to make a video recording of everything that is giving you problems which allows us to see exactly what’s happening. These insights enable us to diagnose problems quickly and it’s one of the tools we use ourselves when we create videos to help our fellow RockStars.
Everything to do with your Sparkzio site, published site and/or Amazon S3 for M3, AmaLuv, and Build Digital Assets is a Sparkzio Product when you submit your ticket. Providing the Site ID is required, and any Domain URLs and/or Amazon S3 URLs, the Registrar, and the Cloudflare settings for your domain(s) have the benefit of saving time, providing you with the answer quickly (screenshots are may also be useful).
