Guide complete per usare GetMyPage senza andare a tentativi

Steps

1. Open Deeplinks and click New deeplink. If you are sent back to the list, check your email verification and plan limit.
2. Choose a clean handle: short, readable, without spaces, and consistent with your profile or campaign.
3. Select the type: Landing for multiple links and content, Direct link for a redirect, or Chat for an automated conversation with one main link. Check that your plan includes the chosen type.
4. Fill in the public title. It should stay recognizable even when the visitor arrives from a social preview.
5. Enter full destinations with https and check that they are not temporary or private links.
6. Save, return to the list, and verify the status, public URL, available actions, and external opening.

Checklist

• Final handle before sharing.
• URLs use https.
• Public title is clear.
• Status is active only when ready.
• Test from a browser without login.

Avoid

• Changing the handle during a campaign.
• Using shortened URLs when they are unnecessary.
• Publishing a page without testing it on a phone.

Steps

1. Check that your plan includes Chat mode: it is available with Creator and Agency, as well as compatible custom plans. Starter does not include it; the tooltip on the locked option explains the restriction.
2. Open Deeplinks and create a page or edit an existing one. Select Chat: Page style becomes Chat settings, with three tabs.
3. Set the handle, page name and one complete main link using https. When switching from a Landing with several buttons, check which destination remains before saving: Chat does not keep a Landing-style link list.
4. In Profile and photos, enter the display name, an age of at least 18, personality, interests and confirmed facts. Use information you can verify and upload the profile avatar.
5. To enable archive photos, upload up to 6 images you have permission to use and add short, accurate descriptions. Wait for checks and uploads to finish.
6. In Writing style, choose capitalization, punctuation, length and the number of bubbles per reply. Adjust emojis, nicknames, question frequency, signature phrases and words to avoid.
7. In Behavior and invitation, set the conversation tone and link invitation. CTA means call-to-action button: configure its label, tone, timing and the value from 4 to 10 in the Show the CTA by turn field.
8. Save and check the status in the Deeplinks list. Publish when the page is ready; if you use a custom domain, verify that it is active and linked to the correct page.
9. Open the public link outside your dashboard session. Write a message, try sending two messages consecutively, wait for the reply and check that the final button opens the intended destination.
10. Repeat the test on a phone and from the social app where you will share the link. Also test the visitor’s language and a photo request if you have configured the archive.

Checklist

• Compatible plan and active page.
• One main link, tested through to its destination.
• Accurate profile and correct avatar.
• Authorized photos and completed uploads.
• Tone, language and invitation checked as a visitor.
• Tested on a phone and from the social apps actually used.

Avoid

• Confusing page conversations with GetMyPage’s support Live Chat.
• Promising fixed response times or live photos.
• Saving a conversion from Landing without checking the remaining link.

Steps

1. Open your Chat page’s Analytics from the Deeplinks list. Visits and Click retain their usual charts, filters, period and timezone; Click also includes the main link and social links.
2. In Click, read Chat effectiveness: conversations started, conversations with a click, clicks on displayed CTAs and time to first click. Compare visitor messages, bot replies and exchanges for bot-only, manual-only and mixed conversations.
3. In Summary, below the traffic-source notice, select Manage chats. Each entry shows the source social network and language. Scrolling to the bottom loads more conversations automatically; on a phone, use the back arrow to return to the list.
4. Write your message and select Send, or use Send CTA to offer the main link. Opening the modal, reading and sending manual replies do not stop the bot.
5. Use Stop bot in the selected conversation to pause automatic replies, including those still queued. Start bot resumes with the visitor’s next message, without sending a backlog of replies to earlier messages.
6. Check message states and permissions before assigning management to a teammate or integration. Visitors need to keep the page open, or return with the same session, to receive new messages.

Checklist

• Correct period and timezone.
• First main-link click distinguished from social clicks.
• Bot state checked for the individual conversation.
• Read, reply and control permissions granted only to the necessary people and keys.

Steps

1. Set the page name and a short bio. The name should confirm the brand or profile; the bio should explain what the visitor will find.
2. Add only the socials that are truly active. A few reliable links are better than a row of empty or outdated icons.
3. Use badges, online status, location, followers, and a custom icon only when they add trust or real context.
4. If you add follower counts, check the label, username, number, avatar, and profile link for each social network.
5. If you use sensitive content, keep texts and media aligned with the rules of the channel where you will publish the link.
6. Read the page again like a new visitor: it should be clear who you are and what the first step is.

Checklist

• Name is readable on mobile.
• Bio is controlled and free of ambiguous wording.
• Socials are active and verified.
• Follower data matches the profile.
• Display elements are not excessive.

Steps

1. Create one button for each real action. Avoid duplicates with different names but the same destination unless you are measuring a variant.
2. Write clear labels: the visitor should know what happens before clicking.
3. Order the buttons by business or narrative priority. The main link goes first.
4. Choose the icon and button style for recognition, not decoration.
5. Use animations, responses, and promotions only on links that need attention: too many micro-interactions reduce trust.
6. If a destination requires protection, evaluate safe or force safe on the single link.

Checklist

• Each button has one purpose.
• Destinations are tested.
• The first link is the most important.
• Animations are used sparingly.
• Safe mode is evaluated on sensitive links.

Avoid

• Labels like click here without context.
• Five buttons with the same visual priority.
• Destinations that are not accessible on mobile.

Steps

1. Set structure and text first, then choose colors and media. Doing the opposite almost always leads to a confusing page.
2. Choose the background, font, and text color with enough contrast. Check especially light photos with light text.
3. Use avatar and banner when they help identify the profile. If an image is heavy or badly cropped, it harms the first load.
4. Enable the gallery only if the images add value to the visitor's decision.
5. Align button shape, outline, icon color, and text color with the rest of the page.
6. Check mobile: no text should overflow and no media should cover the first button.

Checklist

• Contrast is verified.
• The first button is above the mobile fold when possible.
• Images are not blurry or too heavy.
• Gallery is active only when useful.
• Style is coherent with the traffic channel.

Steps

1. Create groups for a client, campaign, profile, or project. The group should help you find pages, not just decorate the list.
2. Use notes to remember the page goal, audience, channel, or deadline.
3. Duplicate when you want a variant with a similar base. After duplication, change the handle, title, and destinations before publishing.
4. Deactivate a page when it should no longer receive traffic but you still want to keep its structure or operating history.
5. Delete only when you are sure you will not need to recover or analyze it.
6. After every critical action, reload the list and check that the status and group are correct.

Checklist

• Groups have operational names.
• Notes are updated.
• Handle is checked after duplication.
• Status matches publication.
• Deletion is used only as a last choice.

Steps

1. Open Domains and add the naked domain, for example domain.com. Do not enter paths or URLs of specific pages.
2. Choose the correct provider in the guide. If your provider is not listed, use the generic instructions.
3. Copy the displayed nameservers and paste them into the domain provider panel.
4. Do not use mixed configurations with old nameservers, half-left records, or external proxies not covered by the guide.
5. Wait for propagation. During this phase the status may remain under verification even if you have just saved everything correctly.
6. When the domain is ready, connect the page that should open from that domain and test from an external browser.

Checklist

• Domain without a path.
• Correct provider.
• All nameservers copied.
• Propagation waited out without removing the domain.
• Page connected after ready status.

Steps

1. Compare the nameservers in the provider with the ones shown in the dashboard. All of them must match.
2. Check that you have not added records or proxies that contradict the guided procedure.
3. Wait for propagation before removing and adding the domain again: doing it often makes the problem last longer.
4. Verify that the connected page exists, is active, and has not reached plan limits.
5. Try the domain without cache, from an incognito window or a different network.
6. If you open a support request, include the domain, provider, nameserver screenshots, and the time of the last change.

Checklist

• Correct nameservers.
• Right provider.
• No unexpected proxy.
• Active page.
• Screenshots ready for support.

Steps

1. Choose page and interval. Use 7 days for quick signals, 30 days for more stable trends, and a custom interval for campaigns.
2. Start from visits and unique visitors. If visits are high but uniques are low, there may be repeated traffic or automatic checks.
3. Look at clicks and CTR. CTR explains better than visits alone whether the landing page is actually convincing.
4. Check social source, browser, and device: they show where the flow works and where it needs retesting.
5. Read countries and bots together. A spike from unexpected countries or crawlers can change how you interpret traffic.
6. Compare before and after an important change, not during the same minute after saving.

Checklist

• Correct period.
• Correct page.
• CTR read together with clicks.
• Social sources checked.
• Bots and countries considered.

Steps

1. Create a tracking link for each channel or campaign: Instagram bio, story, Telegram, X, ads, newsletter.
2. Give it a name that describes source and period, so you still understand it weeks later.
3. Use that tracking link only in the intended channel. If you copy it everywhere, you lose the comparison.
4. During the campaign, look at clicks and CTR by tracking link, not only at the page's total traffic.
5. At the end of the campaign, rename, archive, or note the result before reusing the channel.
6. If you need to change the landing page, note the date: data before and after are no longer directly equivalent.

Checklist

• Clear tracking name.
• One channel per tracking link.
• Period noted.
• CTR compared across channels.
• Landing changes noted.

Steps

1. Segment by social channel: one channel may bring many visits but few clicks, another fewer visits but a more interested audience.
2. Check device and browser. If a social app has a lower CTR, test the link inside that app.
3. Look at countries and times. Off-target traffic may indicate unexpected shares or bots.
4. Evaluate bots and social previews especially in the first minutes after publishing.
5. Measure after single changes: change one element at a time if you want to understand what improved the CTR.
6. Use campaign notes to connect data and decisions.

Checklist

• Source on target.
• Device consistent with the audience.
• Clicks present, not only visits.
• Spikes explainable.
• A/B tests made with controlled changes.

Steps

1. Check that the email is verified. Without verification, some actions on deeplinks, domains, and analytics may be limited.
2. Change first name, last name, username or email only when you are sure: the dashboard may apply a 24-hour cooldown.
3. To change password, use a strong combination: at least 8 characters with uppercase, lowercase, number, and symbol.
4. After a critical change, sign in again and check that the data has been saved correctly.
5. If you do not receive a verification email or code, check spam and the entered address before opening support.
6. Do not share screenshots with tokens, codes, or sessions. Support only needs description and context.

Checklist

• Email verified.
• Data correct before campaign.
• Strong password.
• Cooldown considered.
• No code shared in screenshots.

Steps

1. Open Plan and read the current plan, page limit, and included features.
2. Remember the base behavior: Starter and Creator have a limit of one active page; Agency and Custom use dedicated numeric limits.
3. If you use premium features such as Real-Safe Link, GeoFilter, external analytics, or advanced options, verify plan compatibility.
4. To switch to Creator or Agency, choose monthly or annual billing and, for Agency, the number of links and domains, then start checkout from the dashboard.
5. For needs beyond the available tiers, select Custom and send a detailed request.
6. In the Paddle checkout, review the price, billing frequency, any trial, and renewal; after purchase, use the customer portal to manage billing.

Checklist

• Page limit read.
• Advanced features verified.
• Billing managed from the correct area.
• Detailed custom request.
• Plan checked before activating campaigns.

Steps

1. Open Profile and carefully read the deletion modal.
2. Check active pages, connected domains, tracking, and plan before confirming.
3. If an email code is required, request it and enter it without sharing it with anyone.
4. If you have an active subscription or plan, verify the instructions shown by the dashboard and the connected portal.
5. Download or note what you need before confirmation, because after deletion you may not be able to recover data and configurations.
6. Confirm only when you are sure of the impact on public pages and domains.

Checklist

• Pages checked.
• Domains checked.
• Plan checked.
• Code not shared.
• Consequences read.

Steps

1. Describe goal and result: what you wanted to do and what happened instead.
2. Indicate the dashboard area, page name, handle, domain, or tracking link involved.
3. Add device, browser, social app, and test time.
4. Attach a screenshot if it shows the error, but hide codes, tokens, sessions, or sensitive data.
5. Write the steps already tried: incognito window, different network, DNS wait, verified email, plan checked.
6. Send from the Contact us section or use the channels indicated in the footer when appropriate.

Checklist

• Page or domain indicated.
• Error reported.
• Device and browser written.
• Screenshot cleaned of secrets.
• Steps already tried.

Steps

1. Open API Key from the Agency dashboard, select Create, and use a label that identifies the service, client, or environment.
2. Select only the required permissions. An analytics reader does not need page or domain creation, editing, or deletion.
3. Set an expiry when access is not permanent. A temporary key reduces the impact of possible exposure.
4. Copy the full value immediately because it is shown only once. Store it in a secret manager, never in frontend code, screenshots, or repositories.
5. Send the key in the Authorization header as a Bearer token and test read endpoints before enabling write operations.
6. Review last use, status, and permissions in the list. Revoke an unused or suspicious key immediately and create a replacement.

Checklist

• Recognizable label.
• Minimum permissions.
• Expiry considered.
• Secret kept outside the frontend.
• Revocation procedure ready.

Avoid

• One key shared by several services.
• Write permissions granted for convenience.
• Keys pasted into tickets, chats, or screenshots.

Steps

1. Open Team and select Invite. Enter the collaborator’s account email instead of sharing the owner’s credentials.
2. Choose a preset role as a starting point or Custom. Manually changing a permission automatically makes the role custom.
3. Assign only the required actions: analytics reading, page management, organization, creation or deletion, domain management, and Team management.
4. Grant all pages or domains, or only selected resources. Live search helps locate the correct items in larger accounts.
5. After accepting, the collaborator enters through the Workspace selector. Unauthorized functions remain visible but disabled with an explanatory tooltip.
6. Regularly review members, pending invitations, and last access. Change permissions or remove a member as soon as their responsibilities change.

Checklist

• Correct email.
• Role reviewed.
• Minimum permissions.
• Pages and domains assigned.
• Invitations and members reviewed regularly.

Avoid

• Sharing the owner’s password or session.
• Granting deletion to someone who only needs editing.
• Leaving access active after the collaboration ends.

Steps

1. Social platforms read the link to create previews, verify content, and decide how to show it inside their apps.
2. These openings can arrive before real clicks and can look like visits if they are not filtered correctly.
3. GetMyPage evaluates technical request signals such as network context, browser, webview, headers, and behavior to separate visitors from automation.
4. When Real-Safe Link is enabled, supported crawlers may receive non-public responses; when it is disabled, the page does not apply that global handling.
5. Statistics separate useful traffic, social sources, and bots as much as possible, so numbers should not be read naively.
6. Do not use the first accesses after sharing as proof of conversion: wait for real clicks and coherent trends.

Checklist

• Share the link only when it is ready.
• Wait for real data before judging the campaign.
• Compare visits with clicks and CTR.
• Use tracking links to distinguish channels.
• Open a support request if a social platform always blocks a specific flow.

Steps

1. Enable it when the page and its sensitive destinations should not be read or opened by supported crawlers.
2. When it is disabled, its global rules do not apply; only individual links marked Force Safe remain protected.
3. After enabling it, test the full path: page, click, security passage, final destination.
4. If one button is more delicate than the others, use force safe on that button instead of treating the whole landing page the same way.
5. Real-Safe Link and Deeplinks Tech are independent: the former protects sensitive flows, while the latter manages opening inside apps and in-app browsers.
6. Do not measure success only by visits: check actual clicks and behavior on the protected button.
7. If a visitor reports blocks, collect origin social platform, device, browser, and test time.

Checklist

• Valid final destination.
• Sensitive button identified.
• Force safe used only where needed.
• Real-Safe Link and Deeplinks Tech configured separately.
• Test on iOS and Android if traffic comes from social apps.
• Data read on clicks, not only on openings.

Steps

1. Social apps do not always open links like a normal browser: they often use internal webviews with their own limits.
2. Deeplinks Tech helps manage these differences to keep the path as stable as possible.
3. The system considers source platform, device, browser, and request context.
4. It is especially useful when you publish on Instagram, Telegram, TikTok, Threads, Facebook, or X.
5. After enabling it, test the link in the real channel where you will use it, not only by copying the URL into a browser.
6. If an app updates its internal browser, repeat the tests before attributing the problem to the page.

Checklist

• Main channel identified.
• Test from real app.
• Test from normal browser.
• No random changes during an active campaign.
• Support contacted with exact device and social platform if needed.

Steps

1. Use Force Safe when a specific destination requires the protected path even if the rest of the page can remain normal.
2. Use GeoFilter when you need to allow or block countries for operational, legal, commercial, or anti-abuse reasons.
3. Do not use GeoFilter to fix a broken link: if the URL is wrong, the filter will not correct it.
4. After changing countries or filter mode, test from a condition consistent with the real audience.
5. If you are measuring international campaigns, note the active filters before interpreting country data.
6. Keep an internal note about the reason for the filter, so you do not forget it active months later.

Checklist

• Filter reason written in notes.
• Countries checked twice.
• Test after saving.
• Statistics read knowing that the filter is active.
• Support contacted if an expected country remains excluded.

Steps

1. Enable Google Analytics only if you have a valid ID and an account where you will actually read the data.
2. Enable Meta Pixel when you need to connect measurement and Meta campaigns.
3. Check the plan: some integrations may be unavailable or may make the page incompatible with Starter or Creator limits.
4. Do not expect identical numbers between GetMyPage and external tools: filters, consent, browsers, and privacy blockers can change counts.
5. After entering an ID, open the page and check after some time whether events arrive in the external panel.
6. If you remove tracking, save and retest to avoid leaving empty but active configurations.

Checklist

• Correct GA4 ID.
• Correct Meta Pixel ID.
• Compatible plan.
• Test after saving.
• Data compared across periods, not single visits.

Steps

1. Open Link Scanner from the homepage or the dashboard Tools section and enter a public HTTP or HTTPS URL.
2. Choose the crawler to simulate. Instagram is selected first; social, messaging, and search-engine crawlers are also available.
3. Start the scan and wait for the visitor/crawler comparison. The check follows redirects, metadata, destinations, headers, technical cookies, and security signals.
4. Read completeness and score first, then open each check. An unavailable item scores zero and is kept separate from a failure.
5. Open the technical comparison when you need to understand which final URLs, destinations, or content differ between the two views.
6. Use history to repeat or compare two scans. On the public page it stays on the device; in the dashboard it is saved to your personal account.
7. Inside a Team workspace the scanner does not become shared: history and reports always remain personal to the authenticated user.

Checklist

• Public, complete URL.
• Crawler matching the channel to verify.
• Score read together with completeness.
• Visitor/crawler differences checked.
• Historical comparison run after major changes.

Steps

1. Check that the workspace owner has an active Agency or Custom plan. GetMyPage administrators can connect with no plan limit.
2. In ChatGPT or Codex, open Plugins, search for GetMyPage, open its details, and select the plus button to install it.
3. When prompted, connect your GetMyPage account, select the workspace, and review the permission summary. Start a new chat after installation.
4. In Claude, add a custom MCP connector; in Claude Code, add an HTTP server. Use exactly https://mcp.getmy.page, without adding /mcp, and complete GetMyPage sign-in.
5. Return to the AI client and verify that the connection is active. Ask it to read the workspace or list pages as a first test.
6. Each user connects their own ChatGPT, Codex, or Claude account: GetMyPage does not require shared OpenAI or Anthropic accounts.

Checklist

• GetMyPage plugin installed and enabled in ChatGPT or Codex, or exact endpoint configured in Claude.
• GetMyPage account is verified.
• Correct workspace selected.
• Connection visible on the MCP page.
• First workspace read completed.

Avoid

• Adding GetMyPage as a custom MCP connector in ChatGPT or Codex.
• Using https://mcp.getmy.page/mcp in Claude.
• Entering manual OAuth credentials in Claude.
• Sharing one connection between different people.

Steps

1. Use workspace_get so the assistant can read the effective role, resources, and capabilities of the connection.
2. Owners can manage pages, groups, domains, DNS setup, analytics, API keys, teams, and MCP connections.
3. For a team member, configure ordinary scopes, MCP scopes, and access to all or selected pages and domains in the role.
4. Destructive operations can be run directly by the assistant when the AI client and GetMyPage permissions allow them.
5. API key secrets are shown only once when created or rotated: ask the assistant to store them only in the intended destination.
6. Review Activity on the MCP page to identify recent authorizations, changes, and revocations.

Checklist

• Member role is correct.
• Ordinary and MCP scopes are aligned.
• Pages and domains are assigned.
• Destructive operations are configured in the client to your preference.
• Activity reviewed after critical changes.

Steps

1. Attach the image or video and state where to use it, such as avatar, banner, background, gallery, or button media.
2. If the client supports MCP file inputs, the assistant calls page_media_upload with the attachment and GetMyPage downloads it from the temporary signed link.
3. For a file already available at a public HTTPS URL, the assistant uses the separate page_media_import_url tool.
4. GetMyPage validates the actual content, limits files to 25 MB, and normalizes supported videos to MP4.
5. The tool returns tmpSession and mediaReference; the assistant immediately includes them in page_create or page_update.
6. Only if the client cannot forward a file to the tool, the assistant automatically creates a 15-minute one-time link and shows it without waiting for you to ask.

Checklist

• Media destination clearly stated.
• File is under 25 MB.
• Supported image or video format.
• tmpSession reused in the final edit.
• Page checked after saving.

Steps

1. If ChatGPT or Codex cannot see GetMyPage, check that the plugin is installed and enabled, then start a new chat.
2. If Claude cannot find the server, verify that the URL is exactly https://mcp.getmy.page and does not redirect to another domain.
3. If OAuth does not start in Claude, remove any manually entered client ID or secret and add the connector again as a custom remote server.
4. If GetMyPage confirms authorization but Claude shows an error, remove the connector from Claude, revoke the connection on the MCP dashboard, and create a fresh connection.
5. Check the active plan, email verification, team status, and the selected member's MCP permissions.
6. If Claude shows a reference beginning with ofid_, keep it so Anthropic support can trace the failure after token issuance.
7. To stop access immediately, use Revoke on the MCP page. Access and refresh tokens for that connection are invalidated together.

Checklist

• OpenAI plugin installed and enabled or exact Claude URL.
• No manual credentials in Claude.
• Valid plan and verified email.
• Old connection revoked before retesting.
• ofid_ reference saved if the error continues.