One moment, checking your payment.
We can't find a payment for this link. If you've just paid, use the Start your setup button on the payment page. If that doesn't work, write to hello@shifter.co and we'll sort it out.
We couldn't check your payment just now. Try again in a minute, or write to hello@shifter.co.
Preview: no payment was taken. This is a made-up buyer.
Set up Gear 1.
Seven steps, about 45 minutes in all, and you can come back to this page. Steps 1 to 5 set your start date: it's the business day after our start email, or a later date that email names.
Your Shifter dashboard opens soon. Until then, you approve each key step by email, as your Order sets out.
Only what the work needs. No passwords, ever, and nothing personal about your customers.
The traffic guarantee needs website, Search Console and Analytics access before your start date. We check whether you qualify before work starts, and tell you in writing. Guarantee for qualified clients. Conditions: clause 2.3 of your Order.
If you're eligible for the traffic guarantee, its 90 days count from the day your rebuilt site goes live, as long as it keeps your domain and GA4 property. If it isn't live by day 90, or the rebuild ends before go-live, they count from your start date.
Your company and website (today)
Why: checkout doesn't collect them, and your Order needs them.
- Your company's legal name, and the name you trade under if it's different.
- Your business address.
- Your tax ID (VAT number or EIN), if you have one, for your invoice.
- The website we work on.
- Any other address you publish on, such as a help or docs subdomain (help.yoursite.com), with its platform and who publishes there.
- Up to 2 other public sites on your domain for us to optimize, such as a help or docs subdomain (help.yoursite.com), with each one's platform and who publishes there. With your main site, that makes 3. They need to be in the same Search Console property as your main site.
Once we have these and your approver (step 5), we add them to your Order and email you the completed copy within 2 business days.
Or write to fabian@shifter.co yourself.
Website access (before your start date)
Why: so we can publish your approved articles and make the fixes on your change list. If we can't have a user, your developer publishes them instead.
A website-only user for fabian@shifter.co: pages, blog, redirects, sitemap settings, site-wide header code and root files. Leave contacts, conversations, recordings, customer records and payments switched off. We never ask for a password.
Choose your site tool
WordPress
- In your WordPress admin, open Users, then Add New User.
- Enter a username (for example
shifter) andfabian@shifter.coas the email, and choose the Editor role. - Tick Send the new user an email about their account. That email lets us set our own password, so none is shared.
- Editor covers pages, posts and their titles. Redirects and other site-wide settings need more than Editor, so we send those changes in writing for your developer. Please don't make us an administrator if it would show customer, order or form records.
Webflow
- Open Workspace settings, then Team.
- Click Invite member, enter
fabian@shifter.coand choose a role that can edit and publish the site.
If adding a seat would cost you, email fabian@shifter.co before you add us.
Framer
- Open the project and click Invite.
- Enter
fabian@shifter.co, choose Editor and send. If you see extra permissions, turn on Deploy so we can publish.
On most paid Framer plans an editor takes a paid seat. If it would cost you, email fabian@shifter.co before you add us.
Built in code, or something else
Email fabian@shifter.co with what you use and who publishes for you. We agree the route by email. Where we can't have a user, we send each approved page and each fix ready to publish, and your developer publishes it within 5 business days.
Gear 2: your other sites. If you can, add us the same way on each site you named in step 1. Where we don't have a user, we audit the site from its public pages and send its changes as written steps for your developer.
Or write to fabian@shifter.co yourself.
Google Search Console, every site you own (before your start date)
Why: it shows which Google searches bring up your pages, and whether Google has indexed the new ones. Your reports use it too.
Which sites: your main site and any help or docs subdomain. If you use a Domain property, one invite covers all of them.
Which sites: Your main site and every site you named in step 1. Use a Domain property, so this one invite covers all of them. No Domain property yet? Email fabian@shifter.co, and we send the steps.
fabian@shifter.co
- Open Search Console and choose your site.
- Open Settings (bottom of the left menu), then Users and permissions.
- Click Add user and enter
fabian@shifter.co. - Choose Full and click Add. Repeat for each site.
We ask for a Full user so we can ask Google to index new pages and read your search figures. We use it for nothing else. You can remove us at any time, and we tell you when the work ends. Removing us before day 90 can end the traffic guarantee.
No Search Console yet? Email fabian@shifter.co, and we send the setup steps.
Google Analytics (before your start date)
Why: it shows the visits that come from Google and from ChatGPT and other AI assistants, and which pages they land on. We use it for your site-level reports and the traffic guarantee.
fabian@shifter.co
- In Google Analytics, open Admin (the gear, bottom left).
- Under Property, open Property access management.
- Click +, then Add users, and enter
fabian@shifter.co. - Choose the Viewer role and click Add.
Gear 2: if your other sites send data to the same GA4 property, this one invite covers them.
Sites that send data to a different GA4 property don't count toward the traffic guarantee.
We read site-level reports only and never export user-level data. You can remove us at any time. Without this access, the traffic guarantee can't apply. Removing us before day 90 can end the traffic guarantee.
Use another analytics tool? Email fabian@shifter.co with which one. The traffic guarantee needs a GA4 Viewer, so without one you can start without the guarantee.
Confirm for the traffic guarantee: no site migration or domain change on your site in the last 90 days, and none planned before the end of your first 90 days with us. Any redesign or tracking change in the last 90 days, or planned before your start date: ___
Confirm for the traffic guarantee: no site migration or domain change on your site in the last 90 days, and none planned until 90 days after your rebuilt site goes live, other than the rebuild you ordered from us. Any redesign or tracking change in the last 90 days, or planned before your start date: ___
This counts once it reaches us by email: use the button and fill in the blank, or answer it at the end of your step 1 email.
Your approver (before your start date)
Why: your approver, or your backup, approves our work or asks for changes. We send everything to both.
- your approver's name and email, and a backup's if you want one.
The approver has 2 business days to decide on each batch of up to 10 articles. We publish approved articles within 5 business days, or, if your developer publishes, we send each one to them within 1 business day and they publish it within 5.
Or write to fabian@shifter.co yourself.
Your material (by day 5, more any time)
Why: every article is written from what your team knows: how the product works, what buyers ask, and what customers got from it. The more we have, the less we guess.
What helps most
- product docs, setup guides or help articles;
- notes or transcripts from sales conversations, with names and personal details removed;
- case studies or customer stories you're allowed to share;
- anything that answers a buyer's question, such as FAQs, proposals or onboarding emails;
- anyone on your team we can quote by name, and how to reach them.
How to send: Email your files to fabian@shifter.co, or share a folder with that address rather than "anyone with the link". Notes and documents only, no audio or video.
We copy what you send to our own systems and use it only for your work, with AI tools only where model training is off. We delete our copies within 60 days after your service ends, or sooner if you ask.
A few questions (as soon as you can; they don't change your start date)
Short answers are fine, and a link instead of an explanation is fine. From your answers we draft 20 buyer questions for the work to target and send them by day 5. You have 2 business days to agree them or ask for changes; if we don't hear back, the list stands.
No one controls what ChatGPT, Gemini or Google's AI features say, so we never promise a ranking, a citation or a recommendation.
- In one sentence, what do you sell and who buys it? What name do buyers use for this category?
- Which job titles choose a product like yours, and which sign off the budget?
- Your best-fit customers: their size, and their industries, best fit first.
- Where you sell: countries and languages. We track the US unless you tell us otherwise.
- Your top 3 to 5 competitors, with their website addresses.
- The names that count as you: brand, product names, old names and common misspellings.
- The five questions that matter most to your pipeline, typed the way a buyer would, naming no brands.
- Your pricing page address. Are all current prices on it?
- Your integrations page address, and which integrations have their own page.
- Your G2, Capterra, LinkedIn and Crunchbase addresses, and who can edit each.
- Your publishing rules: review steps, legal or brand limits, and any pages we must not touch.
- Slack or email for day-to-day messages? (For Slack, we send a shared-channel invite by day 3.) Weekly updates come by email on days 7, 14, 21 and 28 to your approver and backup. Who else should get them?
- What could your first press release announce? For example a launch, a new integration, a customer you can name, or a milestone. (We send you the draft by day 21.)
- Do you have numbers we could use for a data study, such as product usage totals or survey results? Only totals or anonymized figures, please: no names, emails or other personal data about your customers or users. (We propose the topic, method and sources by day 30.)
Or write to fabian@shifter.co yourself.
We couldn't send that. Please email fabian@shifter.co.
Authority Accelerator
It runs for 45 days from your start date, and needs no access beyond your Gear's steps above.
Website rebuild & migration
Three steps. Your rebuild's dates count from the business day after we confirm by email that these steps are all in, or from your start date if that's later.
- By rebuild day 10: your sitemap and page list, with up to 15 pages plus your existing posts.
- By rebuild day 17, or 3 business days after your page list stands if that's later: a homepage design and an inner-page design in your brand, for your approver to approve within 3 business days, with one round of changes.
- By rebuild day 30, or 8 business days after your designs stand if that's later: the new site on a staging address.
- After that, the go-live steps, and 30 days of fixes to our build after go-live.
Your press release
Why: the Accelerator includes one press release, which we send to your approver by day 21. It goes out in your company's name, so the right person should approve it.
- If someone other than your approver (step 5) should approve the release, their name and email.
- If you know already, what could it announce? For example a launch, a new integration, a customer you can name, or a milestone.
Rebuild: platform and host
Why: we build your new site in your own account, so it stays yours.
Choose one
WordPress, on your own hosting
Invite fabian@shifter.co to your hosting account limited to the new site: a user on a new staging site, or an Administrator user on a fresh WordPress install there, with no access to your current site's database, backups, form entries, DNS or billing. If your host can't limit it, you or your developer create the staging site and give us the WordPress user only.
A code site on your own Vercel or Netlify account
- Invite fabian@shifter.co to your Vercel or Netlify team with the Developer role. On Vercel, adding a member needs a paid team.
- If your team also holds your current site and can't limit us to the new one, create a separate team for the new site in your name and invite us there without billing access. Any team-plan fee is yours.
- Also invite fabian@shifter.co as a collaborator on the site's repository in your own GitHub or GitLab account.
- For forms, and for a cookie banner if yours is a WordPress plugin today, set up a form service and a consent tool in your own account, and give us only the settings we need to connect them, with no access to submissions.
If adding a member would cost you, email fabian@shifter.co before you add us.
- Webflow and Framer aren't offered for the rebuild.
- If your new platform isn't the one you use today, we move up to 150 of your existing posts. More are quoted separately.
- The account stays in your name. We never ask for your domain registrar, DNS or billing logins. At go-live we send the DNS change as written steps, and you or your developer make it.
Rebuild: your current site
Why: we move your existing pages and posts to the new site, and redirect every old address that changes.
- If you gave us a website user in step 2, that covers this.
- If not, a content-only export of your current site: pages, posts and media, with no users, comments, form entries or orders.
- WordPress's own export tool includes comments and author details, so on WordPress please add a website-only user instead, as in step 2, or have your developer send a content-only export.
- For another platform, email fabian@shifter.co and we send the steps for a content-only export. You can also add a website-only user, as in step 2.
We rebuild your forms to send to the same places as today. We never move form submissions, customer records or payments.
Rebuild: brand and pages
- Your logo files, brand colours and fonts, and any page you want dropped from or added to your current site, or tell us you have none. Your rebuild's dates wait on this answer.
- Our platform (WordPress, Vercel or Netlify): ___
- Our hosting company, for WordPress: ___
- Our repository (GitHub or GitLab), for a code site: ___
- Our form service and consent tool, for a code site: ___
- Logo files: attached, or a link: ___
- Brand colours: ___
- Fonts: ___
- Pages to drop (or "none"): ___
- Pages to add (or "none"): ___
Marked as done. We check on our side and email you if anything's missing.
That's everything for now
Thanks. Within 2 business days of your access being in, we email whether the traffic guarantee applies and, if it does, your start date, and tell you if anything is missing. Your first weekly update comes on day 7, or the next business day if that's a weekend.
Once your rebuild steps are all in, we email you to confirm. Your rebuild's dates count from the business day after that email, or from your start date if that's later.
Confirm for the traffic guarantee: no site migration or domain change on your site in the last 90 days, and none planned before the end of your first 90 days with us. Any redesign or tracking change in the last 90 days, or planned before your start date: ___
Confirm for the traffic guarantee: no site migration or domain change on your site in the last 90 days, and none planned until 90 days after your rebuilt site goes live, other than the rebuild you ordered from us. Any redesign or tracking change in the last 90 days, or planned before your start date: ___
- Our site tool: ___
- Our developer's name and email: ___
- Who publishes on our site: ___
Confirm for the traffic guarantee: no site migration or domain change on your site in the last 90 days, and none planned before the end of your first 90 days with us. Any redesign or tracking change in the last 90 days, or planned before your start date: ___
Confirm for the traffic guarantee: no site migration or domain change on your site in the last 90 days, and none planned until 90 days after your rebuilt site goes live, other than the rebuild you ordered from us. Any redesign or tracking change in the last 90 days, or planned before your start date: ___