Back to the journal

Facebook

The Facebook Page website field should be the same hub

Pages still send people who do not live on Instagram. Put one indexable URL in About → Website, and point action buttons at the same shop, booking, or map — not at a second, forgotten tree.

September 26, 20265 minLinkForge Editorial

Facebook Pages still have a Website field, and it still gets tapped by people Instagram does not have: local customers, older buyers, relatives planning a visit, and anyone who arrived from an event or a Marketplace conversation. The classic own-goal is pasting a Facebook Event URL that ended on Tuesday, or a Linktree you stopped updating when you “moved everything to Reels.”

Use the same public hub you use on Instagram. One page, one title, buttons for the actions a Page visitor actually needs. Facebook can be a citation — a place your name appears with a link — while the hub remains the document you can edit, describe, and keep in a sitemap. How that document ranks as a page is ranking a link-in-bio URL. The field itself is simpler than the ranking question: do not point it at a dead event.

What to put in the field, by kind of Page

A shop or a maker. The hub’s first button is the current collection or the current made-to-order form, not the homepage of a platform if that homepage is a maze. Maps and a reviews link sit below for people who need to visit or to trust. Patterns: Google Maps in the bio, Google reviews.

A café, clinic, or salon. First button: book, menu, or WhatsApp during real hours. Second: directions. Third: call, if the phone is staffed. The Page’s hours and the hub’s hours must match. Facebook will show its own hours; if they disagree with the website, people believe the one that is more convenient and then get angry.

A creator. The hub matches Instagram: one hero for this month, quieter links under it. Do not build a “Facebook-only” link list you will forget. The audiences differ. The address should not.

An event promoter. The field stays on the hub. Individual events are buttons or a dated Now line. When the event ends, you change the button. The Website field keeps working for the person who saved the Page.

Action buttons are not a second strategy

Pages can show action buttons: Book, Shop, Call, Send message. Those should hit the same destinations as the hub. If “Shop” goes to Shopify and “Website” goes to an abandoned link list, you have two businesses. Pick a system of record. Usually that is the shop or the booking tool, reached through the hub so you can add a size guide or a parking note without begging the action button to grow a paragraph.

Check both on a phone. Desktop Page layouts hide mistakes that mobile makes obvious: a website row that overflows, an action button that opens an app the visitor does not have, a Messenger thread that nobody answers. If you will not answer Messenger, remove it as the primary action and say where you do answer.

Set it, then verify like a customer

  1. Publish the hub with a title a local searcher understands. Create it on LinkForge. Five links on the free plan cover shop or booking, directions, reviews, contact, and one seasonal extra. Pro at 7€/month is the custom domain and SSL when every profile on the internet should show your name, not a tool host.
  2. Facebook Page → About (or Settings → Contact and basic info, depending on the layout Facebook is showing you this month) → Website. Paste the hub. Save.
  3. Open the Page in the Facebook app on a phone that is not an admin. Confirm the website row taps and lands on the hub, not on a login wall and not on the old event.
  4. Tap the action button. Confirm it and the hub’s first button do not contradict each other.
  5. If you run ads, the ad’s URL can be a tagged copy of the same path (utm_source=facebook&utm_medium=ad). The organic Website field can stay clean or carry a stable utm_medium=page. Do not send ads to a one-off shortener. The tagging rules are UTM parameters.

Personal profiles have a tighter website slot than Pages. The rule is the same: one hub. If you are a person and a Page, the Page gets the company hub and the profile gets you, and you say so in the first line so relatives and customers land in the right place.

Events, Shop, and Groups

An event’s ticket button can go straight to the ticketing platform for that night. The Page website should remain the hub, where next month’s date will appear. When the event is over, edit the event or leave it clearly past. Do not leave “tickets” as the Page’s permanent website.

Facebook Shop, if you already fulfill there, can be the action button. Keep the hub for anything that is not a SKU: appointments, allergies, a menu PDF, a wedding consult. That is the same split as Instagram Shopping versus a link in bio.

Groups are worse long-term homes than Pages. A group’s pinned post with a URL goes stale. If the group is where your people are, pin the hub and say which button to tap. Still put the hub on the Page, because groups get archived and Pages get searched.

A quarterly clean-up

Read the Page’s About section next to the hub. Hours, address, phone, and the description’s first sentence should agree. Delete action buttons you do not service. Replace any event URL that has passed. Look at Page insights only for a narrow question: are people tapping the website, and does the hub’s analytics show those visits doing the thing you care about (book, call, buy)? If the Page sends visits and the hub shows no taps, the first button is wrong for this audience. Facebook traffic often wants hours and a map before it wants a brand story. Reorder for the people who actually arrive, or add one line of hours in text above the buttons.

The Website field is a citation you can keep true with one paste. Point it at the hub, point the action buttons at the same reality, and update the offer on the page — not by inventing a second link list for a network you open twice a week.

Create my page — Pro is 7€/month (~$7)

Free to start. Pro is 7€/month (~$7 depending on exchange) for a custom domain and full SEO controls.