Category: SWXL Templates

OVERVIEW:

Import URLs that are ranking for keywords in SEOClarity that we do not already have in other URL templates. We run a simple matching process, and if there are any URLs that are already in the valid site map, we do not import them. All other URLs are imported into the “Static URLs” template 102.

PROCESS:

Run: https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/SiteMapManager/trunk/util/import-stat-urls-to-smg.sql

Run script to find EDW URLs that are not going to be generated in the standard URL templates.
Add them to the Static URL template, or decide whether or not they need their own URL templates (you may need to contact the SEO Specialist).

Run: https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/SiteMapManager/trunk/util/import-edw-urls-to-smg.sql

DEPENDENCIES:

• Import/Update Hotel Property Data
• Request/Collect: Top 100 Regions

OVERVIEW:

Generate default Region Priorities according to the documented process below. Then give a special boost to the Top 100 Regions the Client identified directly.

PROCESS:

1. Run 03a-Updated_Latest_Data.sql
2. Generate Region Priorities – Primary Language:
   https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/KWGeneration/trunk/KWExplosion/preprocess/03b-update_region_priority.pl with “-d”
3. QA Region Priorities Generated
4. Clone Region Priorities to 2nd and 3rd language:
   https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/KWGeneration/trunk/KWExplosion/preprocess/03c-update_region_priority-non-primary.sql

NOTES:
https://docs.google.com/a/myersmediagroup.com/document/d/192C33h2Y-Glo4lcJfTX5mj4_yDil_HEbT4wrGH3zsdw/edit

OVERVIEW:

Primary Language Only. One common method used to adjust priorities of keywords is to group them in collections with boost values which influence the priorities of those keywords. Note that only entries with a boost value need to be updated and while a SWXL may have any number of boosted collections, the standard ones are:

• User Association keywords. We boost priority for keywords in this collection, as most of the keywords are important. This is especially important for new keywords we didn’t have in GKMS before because they will have no other data to give them priority.
• ‘SV = 0’ keywords. If keywords have no real search volume, i.e. no one searches for it, we should lower its priority.
• ‘Expedia POS Top Targets’. If the client specifies Top Target keywords, these need to be in a boosted collection to ensure they get placed in G1.

PROCESS:

• Review the dbo.collection_info.query column which describes how each collection is updated.
• Update the dbo.collection_info.last_updated column

Run the scripts located in:
https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/DB/tools/db_builder/GKMS/common/USP/update_collection/

NOTES:

See http://gkms-{pos}.mmg.local:8080/collections.aspx for an admin overview of the database tables.

DEPENDENCIES:

• Final approval after GSI Review received or imminent.

OVERVIEW:

Run ILG. Since ILG can take a long time to complete, it is usually beneficial to run ILG early while the final SWXL is still being reviewed and approved. After final approval, if there are no changes then we will already have ILG complete and save many hours of waiting.

https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/URLPriority/note.txt

PROCESS:

13. Generate ILG: Run script to generate relations. It could take about 10-15 hours for a mid-size POS. May need to run when server is not under high load.

exec up.usp_url_swxl @url_swxl_parameter_id = @url_swxl_parameter_id;

14. More QA, make sure results in up.URL_SWXL_Relation are the same as specified in up.URL_Link and up.KW_Link

15. At this point, one can proceed with the same scripts noted in KW-based SWXL

https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/ILG/trunk/qa/ILG_QA_Report.sql

https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/ILG/trunk/util/execute-usp-generate-swxl-tables.sql

NOTES:

• Small Points of Sale typically take about 5 hours.
• Large Points of Sale could take 8 hours or more.
• For status, check the up.URL_SWXL_Status table.

PROCESS:

https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/KWGeneration/trunk/KWExplosion/preprocess/02-all.sh

https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/KWGeneration/trunk/KWExplosion/preprocess/03a-Updated_Latest_Data.sql

https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/KWGeneration/trunk/KWExplosion/preprocess/03b-update_region_priority.pl

https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/KWGeneration/trunk/KWExplosion/preprocess/04-Airport_Region_Mapping%25.sql

NOTES:

Running .sql scripts via build-db.pl whenever possible is recommended since it handles most variable substitutions transparently.

Set up new instance of SWXL DB for POS – Primary Language
Set up new instance of SWXL DB for POS – 2nd Language
Set up new instance of SWXL DB for POS – 3rd Language

OVERVIEW:
Cross-reference and import applicable CMS URLs and associated data feeds.

PROCESS:

1. To generate URL/meta-data dump, use:

   https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/SEOCluster/trunk/cms/script/dump-urls.php

   Alternatively, the latest dump is probably available from the latest build_cms-sitemap build at:

   dev:/var/jenkins/workspace/build_cms-sitemap/{lob}-{pos}.1.dump.gz.

   If the Jenkins job is running, wait until it’s finished.
    

2. To import URLs, use:

   https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/KWUrlAssociation/trunk/UserAssociation/script/import-urls.pl

   Note that if there are “Multi-City” pages, they go in the “City” template.
    

3. To import data-feeds, use:

   https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/KWUrlAssociation/trunk/UserAssociation/script/import-data-feed.pl 

4. After import, to check how to handle data feed updates, see:

   https://dev.myersmediagroup.com/mmgsvn/Users/rchung/swxl_queries/Handle-Custom-Template-URL-Change.sql

   For updates, use these same steps but specify new data-feed table names. Then, match ds.SEO_StaticURLs URLs by template_id, set deleted = 1 if not in the new data-feed, e.g.
    

   update ds.SEO_StaticURLs set deleted = 1 where id in (select id from (select * from ds.SEO_StaticURLs v where v.template_id = 3001 and url not in (select url from ds.flights_airports_3001_20130930)) selected) 

5. Manually delete old kwg.Template_DataFeed entries. Optionally clean up old data-feed definitions.
6. Repeat for 2nd language
7. Repeat for 3rd language

OVERVIEW:

Because hotel name’s real search volume could be misleading, we calculate the “pseudo real search volume” by multiplying hotel total room nights (or GB) with a factor, so the value is more close to priority order.

PROCESS:

1. Run https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/KWGeneration/trunk/KWExplosion/preprocess/06b-Hotel_RSV.sql and the result is kwg.hotel_rsv.
2. QA Review of Hotel Properties Priority structure.
   A quick way is to compare eSV with the real search volume of the keywords, but this can only serve as a guideline. The best way is to check KW Priority results later and come back to adjust this if necessary.
3. Clone Hotel Properties Priorities to 2nd language
4. Clone Hotel Properties Priorities to 3rd language