Create a new folder on the Client’s YACSS foder and make a copy of the Mass Page Builder Template for the Second round of YACSS
Same with the first round, use the sheet as a basis for the Mass Builder. Still 3 Tiers and don’t forget to randomize the clouds
This is the arrangement of the clouds for round 1
This is an example on how I randomize the round 2 YACSS stacks for Tier 1
You can use https://www.random.org/lists/ to randomize the clouds
Don’t forget to update the cloud name
On the YACSS site, click on ‘My Websites’ tab found on the left
Find the YACSS cloud stack that you generated on the first round
Click on the 3 dots icon found on the right and select regenerate
Select a different template design
Go to the Build Settings tab and update the name to the new main keyword
Change the anchor text to different anchor text but still use branded for Tier 1. The branded anchor text could be a partial or exact match i.e. Lacy Law Firm, Lacy Employment Law Firm, Lacy Law
Target URL is still the service page for Tier 1 or the home page if the client has a single service and location
Change the meta titles based on the updated keyword file. Still input 100 meta titles so that we will still have 100 pages per cloud
Old:
New:
Enter the newly generated Schema. Do not replace the FAQs schema since we will be using the same FAQs
Check on the Image SEO section if the URL is the service page of the client’s website. If the client has a single service and location then target the homepage. Contact Manager if you have difficulties in determining the target URL.
On the Entities Section, remove the Current Entities by clicking on the ‘X’ button as shown below
Click on Browse
And add the latest generated Enitites text file
Also Change the keywords on the Headers Tab
This stack was used for the previous stacks so there will be links in the footer section
Links will be added again once we upload to the clouds
Click on Regenerate once done and start Uploading to the Clouds
Do the Google Stacks Tier 2 and the Tier 2 and 3 Cloud Stacks o n Stack builder, Same process as well as the indexing and the uploading. Don’t forget to mix up the clouds, do not target the same cloud, one cloud must target a different cloud for the Stack Builder
