Category: SWXL Templates

SUBDOMAINS:

For multi-language POS, URLs should be segregated into their respective GKMS’; all others should be marked deleted. For example, gkms_th_en (a secondary-language POS), should have ONLY www.expedia.co.th/en/* URLs, and gkms_th_th (the primary-language POS) should NOT have any www.expedia.co.th/en/* URLs.

Also, there will likely be a lot of strange sub-domains or even full domains outside of the given POS, after STAT and EDW URLs are imported. These should be marked “deleted” in the ds.SEO_StaticURLs feed and SMG re-run to get rid of them. Note that some sub-domains are likely acceptable; discretion required.

SEARCH PAGES:

Search pages within the POS’ domain are likely undesirable; e.g. http://www.expedia.de/Hotel-Search. Remove this similarly.

An easy way to search for these is with a query like

select * from Site_URL with(nolock) where template_id = 102 and url_no_protocol like 'www.expedia.de/%' order by len(url)

or

select * from Site_URL with(nolock) where template_id = 102 and url_no_protocol like '%search' and url_no_protocol not like '%.packagesearch' order by len(url)

MOBILE PAGES:

Mobile pages are generally undesirable; e.g. https://www.expedia.se/m/trips. Remove these pages by marking as deleted in ds.seo_staticURLs

An easy way to search for these is with a query like

select * from Site_URL where template_id = 102 and url_no_protocol like 'www.expedia.se/m/%' order by len(url);

CMS URLs:

CMS URLs canonically end with slashes, but often show up in EDW and STAT without. These should be filtered out manually with something like

For VC deployments:

update ds.SEO_StaticURLs set deleted = 1 where deleted = 0 and template_id = 102 and url like 'http://{domain}/vc/{cms_top_dir}/%[^/]'

For non-VC deployments:

update ds.SEO_StaticURLs set deleted = 1 where deleted = 0 and template_id = 102 and url like 'http://{lob}.expedia.%[^/]'

OVERVIEW:

Incorporate GSI User Modifications

PROCESS:

Incorporate GSI User Modifications

https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/Reporting/trunk/SEO_Toolbar_V2/GKMS/sql/apply-gsi-changes.sql

Changes made in the SEO Toolbar will not take effect until SWXL Auto Refresh is reactivated after the SWXL update. This shouldn’t be an issue if the SWXL Auto Refresh was deactivated before the SWXL update and the specialist was advised not to make changes in the toolbar while the SWXL update is in progress.

DEPENDENCIES:

• Migration ds.swxl-express-panel 0021 applied.

OVERVIEW:

• Generate Summary Tables – “First Update”

PROCESS:

1. Insert a new ‘fm.Summary_Version’ entry with ‘is_live’ = False

   insert into fm.summary_version (version, Last_updated, is_live, Note) values ('',getdate(), 0, '');

2. Update config ‘fm.summary.DbVersion’.

   update config set value = '', note = '', updated = getdate() where component = 'fm.summary';

3. Generate Summary Tables

   exec fm.usp_update_Summary_Historical_All;

4. Copy to both prod01 and gsi.myersmediagroup.com:

   use global_swxl;
   declare @site int set @site = (select id from site where pos = '{POS}')
   
   -- Prod01 (run on prod01.mmg.local)
   use global_swxl;
   exec [dbo].[usp_global_summary_update_all] @site_id = @site;
   update dbo.site set last_swxl_update = getdate() where id = @site;
   
   use seo_toolbar;
   update dbo.site set last_swxl_update = getdate() where id = @site;
   
   -- GSI (run on gsi.myersmediagroup.com)
   use global_swxl;
   exec [dbo].[usp_global_summary_update_all] @site_id = @site;
   update dbo.site set last_swxl_update = getdate() where id = @site;

OVERVIEW:

For all languages, perform the final SEO Interface update POST SWXL generation, so the Client will have the latest SWXL data to analyze, and we can begin importing monthly performance data against the final set of KWs in G1 and G2.

PROCESS:

Run https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/ILG/trunk/util/update-live-swxl.sql.

Regardless of the POS language, most will have English terms show up from EDW data. Therefore, we should import the default exclusion-list patterns from the E.com US POS.

Additionally, if there is an active SWXL from a region sharing the same language (e.g., AT-DE, ES-MX, etc.) we should consider importing the other (existing) POS’ exclusion list and patterns.

The exclusion list patterns are contained in the following tables:

• Bad_KW_Pattern
• Negative_KW_Pattern
• Site_Brand_KW_Pattern

Clone Exclusion Data/Patterns to 2nd Language
Clone Exclusion Data/Patterns to 3rd Language

The tasks associated with this grouping are those that allow us to provide an SEO Specialist with an easy-to-review/edit workbook that will contain Top Regions, Root Terms, LOB KW variants, URL Templates, etc.

DEPENDENCIES:

• For New SWXLs:
  • Generate/Import: All Root Terms to send to STAT for rank & rSV
  • Generate/Import: All Research Terms to send to STAT for rank & rSV”
• For Update SWXLs:
  • Import/Update: Latest G1-2 STAT Rank and SV Data

OVERVIEW:

Run the KW-URL Association processes for STAT Google, Bing and Yahoo.

PROCESS:

Run with the “-a” parameter:

https://dev.myersmediagroup.com/mmgsvn/KMS/trunk/DataSources/STAT/script/merge.pl

 

OVERVIEW:

Client Review of:

• KW priority
• SWXL groups
• G1 Top Keywords: Exclusions, URL Associations, General G1 Membership

For all languages, communicate with the PMs which timestamps refer to the live and updated versions.

For example:

Summary versions:
Last update before Live: 005.008.20151117
Production Version: 005.009.20151130
Current Maint. Version: 005.010.20151202

The tasks associated with this grouping are typically those that are done prior to the actual generation of the workbook sent to the SEO Specialist for feedback/input, or are precursor tasks. There are other tasks that may be tagged “IDS” that are grouped in other areas, but are also IDS-type tasks.