A little help goes a long way
Let’s get things
working for you.
A connection question, a website change, or something that does not look right? Start here, or get in touch with Mosh directly.
Email GoodwordGetting your assistant
connected.
Our Goodword for AI guide covers setup, available tools and example requests. The connection uses your purchase email and the six-digit PIN you set on the private claim page.
I have not set a PIN yet.
Open your private claim page after the claim is complete and set a six-digit PIN in the AI access section. Then start the connection from your AI app. If payment is still pending, finish the claim first.
My email or PIN is not working.
Use the email associated with the completed website claim. Enter your PIN only on Goodword’s authorization page. You can set a new PIN from the private claim page; this invalidates existing connections. If you see a message about too many attempts, wait before retrying.
I lost my private claim link.
Email mosh@getgoodword.ca from your purchase email if possible. Include your public website address and explain that you need help recovering access. Do not send your PIN or tokens.
The app cannot reach Goodword or complete sign-in.
Confirm that the server address is https://getgoodword.ca/mcp and the connection uses OAuth. Start a fresh connection from your app; the Goodword sign-in flow expires after 10 minutes. Ensure your browser allows the Goodword sign-in cookie. If it still fails, send us the app name, exact error and approximate time of the attempt.
My connection worked before, but now asks me to sign in.
A changed PIN, revoked access or expired connection can require a new sign-in. The app can refresh access for up to 30 days from authorization. Reconnect through the app and authorize your website again.
I have more than one website.
Each connection authorizes one website. If several websites match your email and PIN, the Goodword approval page lets you choose. Confirm the website before allowing access. Managing another website requires the corresponding authorized connection.
A clear path
back to the right version.
A change was published that I want to undo.
Ask your assistant to list the site revisions and identify the previous version. After you choose it, the assistant can restore that version as a new revision using the current site revision. Restoring affects the site files in that revision; review the result on your public website.
An edit fails because the revision changed.
Another change was published after the assistant last read the site. Ask it to read the current site and relevant files, then apply your requested change to that version. It should preserve any intervening edits.
Text or a menu item cannot be found.
Ask the assistant to inspect the relevant HTML, styles and data files. The visible text may be rendered by JavaScript or stored in a separate menu file. Precise element editing applies to static HTML; some sites require source-asset edits instead.
A new image does not appear.
Uploading an image creates the file; the page also needs to reference its correct path. Ask the assistant to check the uploaded file and page reference. Goodword uploads supplied images and does not generate them.
My popup does not show.
Ask the assistant to check whether the popup is enabled, its page targets and its delay in seconds. Reload a matching page and wait for the configured delay.
Make sense
of the numbers.
Why are unique visitors different from people or sessions?
Unique visitor counts use anonymous browser cookies. A person can have several cookies across browsers and devices; blocking or clearing cookies can count them again. Claim-funnel visits use a separate 30-minute session cookie. These metrics answer different questions.
Why do daily unique counts add up to more than the total?
The date-range total deduplicates the same browser across the whole range. Daily groups can include that browser more than once. Use the returned total for a period instead of summing group counts.
Why is location missing or inaccurate?
Location comes from an approximate GeoIP database lookup. VPNs, shared networks, missing database ranges and an unavailable database can affect the result. An empty location means unknown; it does not mean the visitor was in a particular place.
Why can I not see earlier visitor history?
Read the trackingSince field in the tool result. Detailed page-view and location history exists only from the start of tracking for that website. Earlier claim-funnel events may still be available, but cannot reconstruct detailed visitor history.
My daily totals do not match my local calendar.
Analytics uses UTC dates, with Monday as the start of the week. Ask your assistant to state the exact UTC range it queried and explain how that relates to your business timezone.
A person
on the other end.
Email mosh@getgoodword.ca for account help, product issues, privacy requests or security reports.
- Your public website URL and the AI app you are using.
- What you were trying to do and what happened instead.
- The exact error message and approximate date, time and timezone.
- A screenshot if useful, with private links, PINs and tokens removed.
Keep credentials private. We do not need your PIN, access token, refresh token or private claim link in an email. For a suspected security issue, describe the affected feature and the steps that demonstrate it without including other people’s data.
To stop all existing AI access to your website, set a new PIN on its private claim page. You can also disconnect the app in its own settings. For access, correction or deletion requests, see our privacy notice.