Page Comparison

Detailed Setup

...

1. POS TASKS

...

POS Task 1

...

...

2. INFRASTRUCTURE TASKS

...

Infrastructure Task 2 -

...

...

3. COMMERCE TASKS

...

Commerce Task 3 -

...

...

Language String, Setting, HTML widget, etc. Task 4 -

...

Configuration Task 5 -

...

Prerequisite Tasks

...

POS Tasks

• POS Task that must be completed first

Infrastructure Tasks

• Infrastructure Task that must be completed first. Remove section if not required

Commerce Tasks

• AW Commerce task that must be completed first

Settings, Language Strings and/or HTML Widgets for this Feature

...

Settings

• AW Commerce Settings that must first be completed

Language Strings

• AW Commerce Language Strings that must first be completed

HTML Widgets

• AW Commerce HTML Widgets that must first be completed

Detailed Setup Guide

1. Step 1 Header

2. Step 2 Header

1. Step 1 Header

• First bullet should provide navigation instructions i.e. Catalog >Attributes >Product attributes

  1. Sub-bullet for step 1. Every step and click should be detailed so that someone could follow with little prior experience.

     1. Sub-bullet for step a. Include screenshots of the step and use skitch to mark up screenshots. It can be downloaded here: https://www.techspot.com/downloads/5705-skitch.html

Expand
title Example of content within a section
From the Aspenware Commerce Plugins>Age Range page in Admin, click View Add Range Types in the upper right corner. Click Add Age Range Type. Enter a name and description for the age range type. To set the date used to compare the customer’s age to the required age range, select: Calculate from Trip Start (this age range type is likely already configured), or  Calculate from Today’s Date (age range based on purchase date), or Specify the Calculation Start Date; the customer’s age on this date will be used to determine if they are eligible for the product based on the age ranges Click Add. Age Range Types can be edited and inactivated, but they cannot be hard deleted without contacting Aspenware.  Age Range types that are set to Calculate from Trip Start or Today’s Date will never need to be edited, unless you would like to edit the name. Age Range Types that are calculated from a fixed date however, will need to be edited each year to adjust for the current year. Image Removed   Hint: Age Range Types should also be adjusted year over year. If age ranges are calculated based on Trip Start, then they will not need to be updated. Once completed for all required age range types move on to create Age Range.

2. Step 2 Header

• First bullet should provide navigation instructions i.e. Catalog >Attributes >Product attributes

  1. Sub-bullet for step 1

     1. Sub-bullet for step a

DELETE CONTENT AFTER THIS LINE

go to the Glossary page and add the key terms Excerpt Include that you added for your configuration guide.

How-to Guide of this page can be found here: /wiki/spaces/DB/pages/1040089511

...

Guide

1. (Optional) Configure specific pages to restrict crawling using robots.txt

2. (Optional) Configure restricted crawling across all pages using robots.txt

3. (Optional) Restrict search engine indexing across the entire shop

1. (Optional) Configure specific pages to restrict crawling using robots.txt

This is recommended to prevent search engines from crawling hidden categories, voucher product urls, and any page that should not be indexed by search engines.

• To restrict only certain pages from being crawled by search engine bots, configure your robots.txt entry for your shop by going to Configuration > Settings > General Settings.

• Locate the robots.txt section and expand it. It will be pre-loaded with some default restrictions setup by nopcommerce.

...

• To disallow crawling of specific pages find the seach engine friendly page name for that product or category.

  • For product pages, open the product editor page in a separate tab and expand the SEO section.

    • Copy the value used in the 'Search engine friendly page name'.
      

      Image Added

  • For category pages, open the category editor page in a separate tab and expand the SEO section.

    • Copy the value used in the 'Search engine friendly page name'.
      

      Image Added

• Back on the robots.txt editor, paste the ‘search engine friendly page name’ in the Localizable disallow paths at the bottom of the list with a / in front of the search engine friendly page name. Repeat for all PDPs that you wish to disallow crawling on.
  

  • For best results, complete this step before publishing the product if possible.

    Image Added

  • Save General Settings and clear store cache.

2. (Optional) Configure restricted crawling across all pages using robots.txt

• To restrict only certain pages from being crawled by search engine bots, configure your robots.txt entry for your shop by going to Configuration > Settings > General Settings.

• Locate the robots.txt section and expand it. It will be pre-loaded with some default restrictions setup by nopCommerce.

• To disable crawling of the entire site enter a / at the end of the localizable disallow path.
  

  Image Added

  
  

3. (Optional) Restrict search engine indexing across the entire shop

• To restrict the entire shop from being indexed by search engines, go to Configuration > Settings > All Settings.

• Search for the Setting: ‘seosettings.customheadtags’ and edit it.

• Add the following value and save.

  Code Block
  <meta name="robots" content="noindex">

• If something is already added to this setting, as it is also used to define Adobe Analytics Credentials, keep what is added to the setting and include the value above on a new line.