Category: SWXL Templates

OVERVIEW:

For points of sale with multiple languages, we need to ensure that URLs with a language-specific string only appear on the correct language site. For example we would not want URLs with ‘%/en/%’ to appear on a non-English site. 

• TH-th vs. TH-en
• JP-ja vs. JP-en
• HK-tc/sc vs. HK-en
• CA-fr vs. CA-en

PROCESS:

The queries below are offered only as an example. Other patterns and language strings might need to be checked as well.

USE gkms_'{POS}';

select count(*) from ds.seo_staticurls with(nolock) where url like '%/en/%' and deleted = 0
select count(*) from smm_url_validation with(nolock) where url like '%/en/%' and is_active = 1

-- update ds.seo_staticurls set deleted = 1 where url like '%/en/%' and deleted = 0
-- update smm_url_validation set is_active = 0 where url like '%/en/%' and is_active = 1

Add new URLs to database, and make sure all URLs are valid

 Add new KW-URL associations (as user reassignments) to database, using import-assocs.pl. 

Use sample script https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/URLPriority/EmptyLinkSlot/1-generate_file_for_review.sql to generate Excel file for review, using template “Sample – US ELS 2017Q1.xlsx”.

Create new DB objects to handle “Custom ILG” request.

• https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/URLPriority/db/table/ILG_Adhoc_KW
• https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/URLPriority/db/table/ILG_Adhoc_Link
• https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/URLPriority/db/table/ILG_Adhoc_Page
• https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/URLPriority/db/table/ILG_Adhoc_Relation
• https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/URLPriority/db/sp/usp_ilg_adhoc.sql

Should have been covered by https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/URLPriority/db/migration/0011.

• Get a list of URLs and their associated keywords (as anchor texts)
• Get KW links allocation from client, or come up with the numbers internally
• Decide how many links to display on existing SWXL pages
• Prefer complete new set of URLs and keywords. If there are overlapped URLs and/or KWs, we can deal with that, but the number of dupes should be minimum
  • Note: For URLs and KWs already exist in SWXL, suggested they get at least as many links as in live SWXL

 

Example

• 21 URLs, 420 keywords. Each URL has 5000 links total and the links are distributed to keywords
• All new URLs. Some keywords already exist in SWXL
• Each URL will get 5000 new links, so 105,000 links total
• Add 5 more links on existing SWXL pages, so we need 21,000 pages to display new links
• Pick top priority pages to display links, in this case 3000 G1 URLs and 18000 G2 URLs

 

This page is a template for the SWXL Empty Link Slots (ELS) process.

OVERVIEW:

Make sure the record counts match between seo_toolbar and the GKMS databases:

• gkms_{pos}.fm.Test_ILG_URL_Info
• gkms_{pos}.reporting.ILG_URL_Info
• gkms_{pos}.fm.Test_ILG_URL_Info
• seo_toolbar.reporting.ILG_URL_Info

PROCESS:

1. Run

   USE gkms_{pos};
   
   select count(*) from fm.Test_ILG_URL_Info with(nolock)
   union all select count(*) from fm.Test_ILG_URL_Info with(nolock)
   union all select count(*) from reporting.ILG_URL_Info with(nolock);
   
   USE seo_toolbar;
   
   select count(*) from reporting.URL_Info with(nolock) where site_id = (select id from site where pos = '{POS}');

Templates 116 and 117 are becoming important templates and we have the sources to update them.  For new updates we should ask if we want to include them and get the latest list from the sitemap.

Top Target Keywords
If the client provided a new list of top keyword targets, import any new terms and add them all to a new “Expedia.(POS) Top Targets” collection for boosting later during Keyword Prioritization.

*Client must provide URL targets as well.*
Create User Associations for all keywords to these URL targets.

Custom Keywords
If the client supplies a custom list of un-prioritized generic keywords and their URL targets, import them into a new collection called “Expedia Keywords”. These do not need
to be boosted in priority. Any market data we have for them should drive their priorities, however they may need to be checked for rSV if we do not have any available data.