Bullet + Notion website setup troubleshooting checklist

Quick triage (5 minutes)

• Confirm you’re on the right environment (staging vs. production) and the correct URL.
• Open the site in an incognito window to avoid cached sessions.
• Capture the exact error text (login errors, translation not showing, 404s, missing nav items).
• Identify what changed most recently (DNS update, Bullet settings, Notion database restructure, Weglot account credentials, theme/template updates).

1) Domain pointing + DNS (GoDaddy)

• Confirm which domain should point to Bullet:
• Staging domain (recommended for tests)
• Primary domain (production)
• In GoDaddy:
• Verify the DNS records match Bullet’s requirements (A records / CNAME as applicable).
• If you just changed DNS, allow for propagation time (minutes to hours).
• Re-check after propagation using a DNS checker.
• If Bullet uses verification/authorization with your registrar:
• Re-run the domain verification flow and make sure you’re using a current verification code.

2) Auth + login issues (Bullet / Notion / vendor accounts)

• Wrong account email (common when multiple admin emails exist)
• Password changed or reset
• The tool is tied to a different “admin” login than expected

• Confirm the correct admin email for each system:
• Bullet account
• Notion workspace access
• Translation vendor account (e.g., Weglot)
• Domain registrar (GoDaddy)
• If a vendor login fails:
• Verify you’re using the right email first (don’t just reset passwords)
• If needed, reset the password and document the final credentials in your internal system
• Confirm the account has permission to manage the specific domain/site

3) Translation setup (Weglot + domain)

• Confirm the Weglot project is configured for the correct site URL (staging vs. production).
• If Weglot requires domain verification:
• Complete the verification step in GoDaddy.
• Re-check Weglot status after propagation.
• Validate:
• The translated version loads on staging
• Language switching works
• Key pages (homepage, ICP pages, solution pages) are translating as expected

4) Notion database structure + publishing/access control

• Confirm which databases should be publishable vs. internal-only.
• Prefer storing “raw” content databases inside a controlled parent database/page so Bullet can respect publish rules.
• For every public-facing content type (ICPs, solutions, pages):
• Confirm the “Published” (or equivalent) flag is required and correctly filtered
• Confirm the view used by Bullet is the filtered view (not the raw table)
• Test:
• A not-published item should not be accessible via a guessed URL path
• A published item should be accessible and render correctly

5) Header, footer, and navigation setup

• Decide your navigation logic:
• Manual ordering in the Notion database (recommended)
• A dedicated “Featured/Show in nav” property (only if you’ll maintain it)
• In Notion:
• Move ICPs and Solutions into the correct order manually (top = first)
• In Bullet:
• Confirm dropdown menus are only used when you actually need nested items
• Keep single-link sections (e.g., Contact, Insights, Knowledge) as normal nav items, not dropdowns

6) Templates + component library workflow (Notion)

• Decide where the component library lives so it doesn’t accidentally publish on the website.
• When reusing components:
• Open the component in Notion
• Duplicate the block(s)
• Move/drag the duplicate into the target page
• Document the exact steps for your team (including the duplicate step) so future pages stay consistent.

7) Newsletter signup integration (Mailchimp embed)

• In Mailchimp:
• Get the embed code for your newsletter signup form
• Confirm it’s the correct audience/list
• In Bullet/Notion page content:
• Add the embed code where the newsletter section should appear
• Verify it renders on staging
• Validate:
• A test signup reaches Mailchimp
• The confirmation email flow works (if enabled)

Final QA (before you call it done)

• Staging domain resolves correctly
• Translations work on staging
• Internal-only databases/pages are not accessible publicly
• Header/footer styling matches the existing site (or is intentionally updated)
• Nav order matches your ICP + Solutions order
• Newsletter embed renders and captures signups

Get help building your Bullet + Notion website