Once a website is approved, active, and unpaused, LocalLinkMatch can show potential opportunities based on the website's approved details and matching preferences.
Use the opportunities shown in LocalLinkMatch as a starting point for professional outreach. A potential match is not an automatic agreement, and it does not guarantee that the other party will want the same kind of connection.
Before you can contact a match
Your website must generally be:
- Approved.
- Active rather than paused.
- Not deleted.
- Connected to a usable contact email.
- Eligible under your account's current activation/payment status.
The other website also needs to be active and able to receive connection requests. LocalLinkMatch prevents a request when the other website is paused, deleted, not approved, or does not have an eligible contact email.
Review a suggested connection
When you see a suggested connection, review it before sending anything.
Check:
- The other website's category and service relevance.
- The location relevance.
- Whether its website type fits the opportunity.
- Any suggested connection or link ideas.
- Whether the opportunity fits your client's standards and audience.
- Whether you can make a specific, honest proposal.
LocalLinkMatch can present matches using service, category, location, and website-type information. Use that information to narrow your options, not to replace your own judgment.
Send a connection request
To contact a suggested website:
- Open the suggested connection from your website's page.
- Review the other website and any suggested ideas.
- Choose whether to include your Google Business Profile link, if available and relevant.
- Confirm that you want to send the request.
- Accept the required introduction acknowledgement if this is your first LocalLinkMatch introduction. This is recorded once for your account and won't be asked again on later requests.
- Send the connection request.
The request is recorded in LocalLinkMatch and an email is sent to the other website's contact address. The recipient can reply directly to the contact email associated with your website.
What the recipient receives
A connection request tells the recipient that a LocalLinkMatch user would like to connect.
The request includes:
- Your website's display name.
- Your website URL.
- Your connection contact email.
- Optional Google Business Profile information, if you chose to include it.
- Any selected connection ideas that help explain how the websites may be connected.
Your website URL is included with a request so the recipient can see which website is involved. This is a platform rule, not an optional privacy setting.
What happens after you send a request
After a request is sent:
- LocalLinkMatch records the request in your account activity.
- The recipient receives an email at the contact email associated with their website.
- The recipient can reply directly to your connection contact email.
- You may not be able to send another request to the same website immediately.
LocalLinkMatch applies a 30-day cooldown after a connection request to the same website. This is intended to prevent repeated requests and gives the recipient time to respond.
If you receive a request
If someone contacts one of your websites:
- The request is sent to that website's client contact email.
- You can reply directly to the sender from your email.
- You can acknowledge the request in LocalLinkMatch after receiving it.
- You can block further requests from that individual website.
- You can block future requests from the requesting agency when that is the right response.
Blocking a website stops further connection requests from that website. Blocking an agency prevents future matches from the requesting agency, not just the individual website that contacted you.
Dismiss a suggested connection
Dismiss a suggested connection when it is not relevant, not suitable, or something you do not want to consider.
Dismissing a suggestion removes it from your current view and records that decision in account activity. It does not send a message to the other website.
Why you might be unable to send a request
| Message or situation | What it usually means | What to do |
|---|---|---|
| "This website must be approved and unpaused to send connection requests." | Your website is not currently active. | Check its review, payment, and pause status. |
| "This website does not have a verified contact email yet." | The other website cannot currently receive a reliable request. | Try another match or wait until it is ready. |
| "This website is not currently accepting connection requests." | The other website may be paused, deleted, inactive, or otherwise unavailable. | Choose another match. |
| You already requested a connection with this website recently | A 30-day cooldown is active. | Wait until the request cooldown has passed. |
| This website is not accepting connection requests from you | The specific website has blocked requests. | Do not attempt further contact through LocalLinkMatch. |
| "...not accepting connection requests from your agency." | The other party has blocked your agency. | Do not attempt further contact through LocalLinkMatch. |
LocalLinkMatch checks these conditions at the time you send the request, even if the match card was shown earlier. That helps prevent a request from reaching a website that has since paused, become inactive, or lost contact eligibility.
Good outreach principles
A connection request is more likely to be useful when it is specific and relevant.
Do:
- Review the other website before contacting it.
- Use a connection idea as a starting point, then apply your own judgment.
- Make sure your own website is accurately represented.
- Use an email address monitored by the right person.
- Respect a lack of response, rejection, or block.
Avoid:
- Sending the same generic request to every possible match.
- Contacting a website repeatedly during the cooldown period.
- Offering a different website than the one shown in the request.
- Using misleading claims about traffic, authority, services, or the relationship you want.
- Trying to bypass an in-platform block through repeated LocalLinkMatch requests.