Live Round Checks Guidelines

After completing their Go-Live prep, the Project Coordinator will post a Live Round check in #checks_fhs, tagging the WCS to ask for a Tech Audit.

Please complete the Tech Audit as soon as possible. If there are errors present, correct them. Restart the Tech Audit to confirm there are no errors, then post a message in the original #checks_fhs thread to say so.

Remember to complete your Go Live preparations (including asking your WCS for a Go Live sweep) before beginning the Live Checks process.

After changing the nameservers and publishing the new site under the live domain name in Wordpress, the Project Coordinator assigned to the build will begin the Live Check by posting in #checks_fhs using the Live Check workflows.

The Project Coordinator assigned to the project will still be responsible for implementing the feedback to the site.

1. The Project Coordinator assigned to the project will submit the Live Check workflow from #checks_fhs.
   1. Change the Airtable project’s Status from Greenlight to Live Check.
   2. Fill out the form as you did for First Round. Specify your assigned PC partner in the new field.
2. Write any design or function outliers in the “Were there any best practices not followed? Why?” field. PCs should explain why certain pieces of feedback may be inapplicable to their build.
3. Your partner will reply in the post thread to say they started their check. If your partner is out of office, contact your Team Lead for a check.
4. The Partner Project Coordinator will use the Live Round Checks form ( SBMM and ENT ) to critique the site linked in the post. A tangible checklist is available if it helps track feedback.
5. The PC who submitted the check (the one assigned to the project in Airtable) will complete the feedback or discuss with the checking PC over any disagreements.
6. Once completed, the receiving PC changes the project status to Live.

The Project Coordinator assigned to the project will begin the Checks process by using a Live Check workflow from #checks_fhs. They will tag their assigned partner to complete the check, or in the case of absence, the Team Lead.

1. When tagged for a check, the PC Partner should read through the answer to “Were there any best practices not followed? Why?” from the Checks post. PCs should explain why certain pieces of feedback may be inapplicable to their build.
2. Open the Live Round Checks form (SBMM and ENT) to critique the site linked in the post. A tangible checklist is available if it helps track feedback.
   1. Make sure all feedback from your personal checklist makes it into the official Live Check form before submission.
3. Compare all major pages (listed below) against the checklist’s related criteria, marking the check form when an issue is spotted. Use the text fields to explain where on the page the issue is. If there are multiple pages or places on the page where the issue is present, note it in the text field.
   1. Homepage
   2. Segmentation (All Activities, All Categories, or Category pages)
   3. Activities (yes, every single activity page)
   4. Any “top-most” foundational pages (first in their menu dropdown if there are multiple related to a topic)
      1. About Us
      2. Contact Us
      3. Etc.
4. Make sure to check each page mentioned above for general criteria as well:
   1. Button/Link function
   2. Mobile friendliness
5. Log into the back end of the site to check Form settings, Lead ID consistency, dashboard connectivity (looking for necessary ASN or Ref tags) and Analytics connectivity.
6. Log into the Dashboard to check for Analytics connectivity.
7. Log into the Analytics account to check that self referrals and traffic from fareharbor.com are excluded in Property settings.
8. Switch to Google Search Console and check that all sitemaps submitted were accepted.
9. After making sure your personal checklist and the Checks form have the same feedback, pressing Submit on the form will post results to the Airtable card for the project.
10. Respond in the original #checks_fhs thread to say your check is complete.
11. The receiving PC (assigned to the project) will complete the feedback or discuss with the checking PC over any disagreements.
12. Once completed, the receiving PC changes the project status to Live.

• Logo Alt Text
  • The logo image used in the menu banner and any other logos used in Jumbotrons, etc., must have alt text that reflects the company name.
• Favicon
  • The site must have a clear, recognizable brand element as a favicon (logo, part of logo, icon that resembles product, etc). It can’t be left blank.

• H1/H2 Missing Location
  • The SEO Specialist’s recommended location keywords from the Pre Sweep should be implemented into headings on Segmentation pages.

• Missing Related Activities
  • If the site has more than one activity, each activity page must recommend similar experiences at some point.
• Dashboard & Website item names mismatch
  • The title of the activity page should roughly match the name of the item in the Lightframe to avoid confusion. It’s acceptable to alter this title based on SEO recommendations so long as it’s obviously still the same item. Doesn’t apply to multi-item activity pages that use Booking Flows.
• ASN Field Accuracy
  • Do all Affiliate Activities have an affiliate shortname connected in the ASN Partner Name field?

• Price Match
  • All prices listed in the lightframe are listed on the activity page.
    • It’s recommended to check at least one weekday and one weekend availability, in case the activity has complex or dynamic pricing.
• From Price Consistency
  • For each activity, is the lowest available adult price displayed in Activity Grids, Featured Activity Rows, etc?

Overall Site

• GBP Contact Consistency
  • The address in the footer should be linked to the Google Business Profile (if one exists). It must have the same contact information and same street address as the profile. Disregard if there is no GBP.
• If FAS (FareHarbor Activity Site) or Affiliate Site:
  • Is there a ASN Partner Name entry in Company Settings?

Page by Page

• Links Broken
  • Do all buttons, image buttons, hyperlinks or contact information link to the appropriate destination?
  • Do any links lead to 404?
  • Do any links lead to a fareharbor.me address?
• CTA Language Doesn’t Match Action
  • Button labels should set clear expectations of what happens when a link is clicked. For suggestions, see the CTA Label Guide.
  • “Book” or similar purchasing verbs only used when Lightframing.
• Hyperlink Language Doesn’t Match Action
  • Hyperlinks should set clear expectations of what happens when a link is clicked.
• External Link Doesn’t Open in New Tab
  • Any outbound links (points to a non-FHS) should open in a new tab.
• Activity Banner Button Accuracy
  • The banner button should point to the parent page (Category, All Activities). If there is no segmentation page, hide the button.
• Booking Flow Priority
  • Is the booking flow organized similarly to segmentation pages on the site?
  • Are there the same categories in overall flows?
  • Is the most popular item more noticeable than the others?
• Booking Flow Search By Date
  • Is there an option to view a calendar of availability or search by date in the flow Lightframe?
• Booking Flow Item Descriptions
  • Does the Lightframe show the item description (if the customer wouldn’t have visited the activity page by the time they reach the Lightframe)?

• Sub-sub Menu Items
  • Do any dropdown menu items include other dropdowns?
• Priority Activities Not Included
  • If there are no categories, are the most popular items available in the menu?
  • If there are categories, are the category pages available in the menu?

• Page Layout Incompatible
  • All pages should be just as easy to use on mobile devices as they are on desktop.
    • No content extending off the screen
    • No awkward gaps of content
    • No content out of order
• No CTA Above Fold

• “Send to” Gravity Form notification
  • Any forms created should have their Send To notification setting changed to a client email address.
• “Reply to” Gravity Form notification
  • The Reply To notification setting for every form must be drawn from a required email field of the same form.
• Lead ID inconsistent – WordPress
  • The Lead ID field in Company Settings must match the Client Record in Airtable and the domain’s Object ID from the client’s Close Lead.
• Lead ID inconsistent – Airtable
  • The Lead ID field in the Airtable project’s Client Record must match the client’s Close Lead.
• FAS: ASN Partner Name
  • For FareHarbor Activity Sites (FAS) only: double check that the company settings ASN Partner Name and Custom ASN Ref fields are filled out as instructed.
• GDPR/Cookie Solution
  • If the client requested and/or is required to have a cookie solution, is one enabled?

• Account Info Not Added to Site
  • The site must have GA4 tracking info in Analytics & Tracking or implemented by Custom Request.
• Account Info Not Added to Close
  • The Fareharbor email account which owns or was given access to the GA4 property must be added to the client’s Close Lead.
• Account Info Not Added to Dash
  • The GA4 tracking info matching the site must be added to the Dashboard’s Analytics & Tracking settings.
• GA4 Property Not Created
  • Each site must have a unique GA4 property, either owned by the client or created for the client by the Project Coordinator. See the GA4 section of the Go Live Process doc for instructions on sharing or creating accounts.
• GA4 Property Exclusions Missing
  • Traffic from the dashboard (fareharbor.com) and self-referrals (from the same domain) must be excluded in GA4 property settings.
• Data Retention Setting
  • Data retention must be set to 14 months in GA4 property settings.
• Sitemap submission
  • All sitemaps must be present and accepted by Google Search Console.
    • /page-sitemap.xml
    • /activity-sitemap.xml
    • /post-sitemap.xml (only when blog present)
    • /sitemap.xml