Community
Showing results for 
Search instead for 
Do you mean 
Reply

Linkedin Broken Again

Accepted Solution Solved
Bronze Contributor
Posts: 1,394
Country: USA
Accepted Solution

Linkedin Broken Again

Looks like LinkedIn has changed their search criteria again.  The format I'm seeing when I look for it online, is ....

 

https://www.linkedin.com/search/results/index/?keywords=[FN}%20[LN]%2C%20domain name&origin=GLOBAL_SEARCH_HEADER

 

Information in brackets is my replacement for what was there.  There were no brackets.

 

It appears that domain name&origin is the company eMail domain like @swiftpage.com. 

 

I tried to build a new search string, but the domain name&origin stumped me.

 

 

John Purdy
ACT! Premium 2016 (V. 18)
Dell XPS Ultrabook with 4GB, Win 10 Pro, & Office 365, 32bit

Accepted Solutions
Solution
Accepted by topic author jnpurdy
‎05-15-2017 10:02 AM
Bronze Super Contributor
Posts: 1,544
Country: United_Kingdom

Re: Linkedin Broken Again

John - Try: https://www.linkedin.com/search/results/index/?keywords={First Name}%20{Last Name}&origin=GLOBAL_SEARCH_HEADER

David Shaw
Act! Certified Consultant since 2001
Office:    +44 (0)1483 714507
Mobile: +44 (0)7977 567 318
E-Mail:    dshaw@act4u.org 

View solution in original post


All Replies
Solution
Accepted by topic author jnpurdy
‎05-15-2017 10:02 AM
Bronze Super Contributor
Posts: 1,544
Country: United_Kingdom

Re: Linkedin Broken Again

John - Try: https://www.linkedin.com/search/results/index/?keywords={First Name}%20{Last Name}&origin=GLOBAL_SEARCH_HEADER

David Shaw
Act! Certified Consultant since 2001
Office:    +44 (0)1483 714507
Mobile: +44 (0)7977 567 318
E-Mail:    dshaw@act4u.org 
Administrator
Posts: 4,024
Country: United_Kingdom

Re: Linkedin Broken Again

Yep, looks like LinkedIn have changed their search URL again.


David's suggestion works for US databases, however {Last name} should be replaced with {Surname} on UK ones.

 

Alternatively, this URL works in either:

https://www.linkedin.com/search/results/index/?keywords={Contact}

I'll request that KB 38551 is updated with this info.